A new keyboard profile should feel like an upgrade, not a file-format puzzle. If you are asking what files Galleon imports, the short answer is: Galleon imports its native profile files for complete layouts, while image files such as PNGs are used for the visual artwork assigned to individual keys. The difference matters. One file can build your control system; the other makes it look the part.
For sim pilots, streamers and productivity power users, getting this right is the difference between a keyboard full of generic labels and a purpose-built command centre for your favourite game or workflow.
What files Galleon imports for complete profiles
A complete Galleon setup is imported through a native Galleon profile or export file, commonly supplied with a `.galleon` extension. This is the file that carries the actual keyboard configuration: key assignments, pages or layers where supported, actions, labels and layout information.
Think of it as the blueprint. Importing the profile tells Galleon what each programmable key should do. A Star Citizen layout might place power, navigation, combat and landing actions exactly where you expect them. A creator layout may group recording, scene control, chat and editing shortcuts into practical sections. The profile file is what turns a collection of commands into a usable system.
Do not try to import a Stream Deck profile directly into Galleon. Stream Deck profiles and Galleon profiles are built for different software ecosystems, even when they cover the same game, application or visual style. A profile made for one device will not automatically recreate its actions on the other.
The safest rule is simple: import the native Galleon file supplied for Galleon. If a download includes versions for more than one device, choose the Galleon-labelled profile rather than the Stream Deck export.
Why a profile file matters more than a folder of icons
Icons are not commands. A folder of excellent-looking cockpit buttons, office shortcuts or racing controls can transform the appearance of your keyboard, but it does not tell Galleon which keystroke, macro or application action belongs behind each image.
A native profile does that mapping work for you. This is especially valuable in command-heavy titles, where building every action manually can become a multi-evening project. It also reduces the risk of putting the right icon on the wrong command - a small mistake that becomes frustrating the moment you need a control quickly.
PNG files and Galleon key artwork
PNG is the image format you are most likely to see alongside a Galleon profile. These files provide the individual key icons: engine controls, ship systems, camera buttons, Discord actions, spreadsheet shortcuts and more. PNG works well because it supports clean graphics, sharp text and transparent backgrounds.
Depending on the profile package and the Galleon version you are using, the PNG artwork may be included within the profile workflow or supplied in a separate icon folder for assignment. Either way, PNG files are visual assets, not full profile imports.
If you are building your own layout, PNG is the practical choice for custom key art. Keep the image clear at the size of the key display. Fine detail, long labels and low-contrast colours may look great on a monitor but become hard to read at a glance on hardware.
A strong key icon has one job: help you identify the action instantly. For a sim setup, that might mean a landing-gear symbol rather than a tiny sentence. For Outlook or Slack, it may mean a recognisable app colour paired with a short, high-contrast label.
Can Galleon import JPG, SVG or other image formats?
Treat PNG as the dependable format for Galleon key artwork. JPG images can be useful source files, but they do not support transparency and can show compression artefacts around text and symbols. SVG files are ideal for designing scalable artwork, yet they may need exporting to PNG before they can be used as key images.
The practical workflow is to design in the format you prefer, then export a finished PNG for the keyboard. That avoids surprises with transparency, sizing and unsupported file handling.
If Galleon does not show an image when you try to add it, convert it to PNG first. Also check that the filename is simple and that the file has fully downloaded rather than remaining inside a compressed archive.
Do not import the ZIP file
Most downloadable profile packs arrive as a ZIP archive. A ZIP is a container, not a Galleon profile. It may hold the native profile file, an icon library, installation notes and alternative versions for different hardware.
Download the archive, extract it to a folder you can find again, then inspect the contents. You are looking for the native Galleon profile file first. If there is an icon folder, keep it with the profile package until the setup is complete. Moving or deleting it too early can make future edits unnecessarily difficult.
A clean folder structure helps, particularly if you run several games or maintain separate creator and work layouts. Keep one master folder for downloaded packs, then create a backup folder for any profiles you customise. That gives you a reliable return point before testing a new layout or changing a large set of assignments.
How to import a Galleon profile without losing your current setup
Before importing anything, export or back up your existing working Galleon profile. This is not just cautious housekeeping. Custom layouts often contain small refinements built over weeks: a preferred shortcut, a reordered page, a macro timing adjustment or a carefully chosen set of icons.
Then import the native Galleon profile from the extracted download folder. Once it loads, inspect the layout before relying on it in a live stream, race session or busy workday. Confirm that the expected keys appear and that the actions match the labels.
Next, test a handful of high-priority controls. For a game profile, start with actions that are safe to trigger outside active play, such as menus, maps or overlays. For a productivity layout, test commands in a blank document or non-critical workspace first. Keyboard shortcuts can vary between regional layouts, apps and personal configurations.
If a key shows the correct icon but triggers the wrong result, the profile imported successfully - the action mapping simply needs adjustment. If actions are missing altogether, you may have selected an icon pack rather than the native profile file, or imported a profile intended for a different device or software version.
Common Galleon import problems
The most common issue is importing the wrong file from a multi-device download. Check the filename and any accompanying installation note. A file made for Stream Deck is not a substitute for a Galleon profile, and a ZIP file must be extracted before use.
Another frequent problem is assuming the artwork files are broken when only their location has changed. If a profile uses separately supplied PNGs, keep that icon folder intact and avoid renaming everything before you have confirmed the layout works.
Finally, do not overlook software versions. If an older profile behaves unexpectedly after a Galleon update, try importing a fresh copy, then reapply only the custom changes you genuinely need. Rebuilding a few personal shortcuts is usually faster than troubleshooting dozens of inherited conflicts.
Build a keyboard that earns its desk space
The best Galleon profile is not the one with the most commands. It is the one that puts the right command in reach when the moment arrives. Native Galleon profile files provide that ready-built control structure; PNG icons give it the visual clarity to perform at speed.
That is why device-ready packs are worth treating as more than artwork. A properly prepared Galleon profile saves setup time, keeps your controls consistent and gives your keyboard a job beyond looking good on the desk. iConCity profile packs are built around that same principle: less time mapping, more time flying, racing, creating and getting things done.