Saving, sharing and the share card
Keeping a look, moving it to another machine, and the poster a theme can draw of itself.
The save bar sits at the top of the screen the whole time the editor is open, so keeping your work never means going to find a panel.
Saving a theme#
The dropdown lists your own themes, plus the built-in you're currently on, plus — New Theme —.
Choose — New Theme —, type a name, press Save (or Enter). That captures everything: the palette, your colour overrides, the editor font, the syntax theme, your part edits and any section CSS. The result is self-contained — it keeps no link to the theme you started from.
With one of your own themes selected, the button becomes Update, which bakes your current edits into it in place. It only lights up when there's something to bake.
Built-in themes can't be overwritten. Start editing one and the bar flips itself to New Theme mode. Names must be unique; a duplicate is refused with A theme with that name already exists.
Delete is the bin icon, and there's a second one on each row of the dropdown. Neither asks for confirmation. Deleting the theme you're wearing drops you back to Semantix Native.
There is no rename. Save under the new name, then delete the old one.
Where themes live#
Themes are stored per user, not per project — under ~/.semantix/USER/ — so they follow you
into every project on this machine. They do not travel to another machine on their own; that's what
export is for.
Note
One setting breaks that rule. Window translucency is stored per project, while the palette is global. So a translucent theme imported in one project will be opaque in another until you set it there too.
Export and import#
Export writes a .semantix-theme.json file to your Downloads folder, named after the theme. It
carries the whole look — palette, editor font, syntax theme, surface edits, part edits, section CSS,
layers and the wallpaper.
It exports what you're currently looking at, unsaved edits included, so you don't have to save before sharing.
Images ride along inside the file as embedded data, which is what makes a theme a single portable artefact that works offline. It also means a theme built on a photographic wallpaper can be several megabytes of JSON. Pictures are downscaled and re-encoded on the way in to keep that in check; SVGs are kept exactly as drawn.
Import adds the file as a new theme and switches to it immediately. It never overwrites an existing theme, and importing counts as a save, so it survives leaving the editor.
Important
Importing a full theme replaces the deeper layers, including by absence. If the file carries no part edits, your current part edits are cleared rather than kept — the point being that you get the look as its author made it, not a mixture. Export your own work first if you want it back.
There is no preview and no undo. Undoing an import means deleting the theme it created.
A file the importer can't read produces no message. The Import button turns red for a couple of seconds and its tooltip changes to That file isn't a valid theme — which you'll only see if you hover it. If an import seems to do nothing, that's what happened.
The share card#
The other icon draws a poster of your theme: a PNG, painted entirely from that theme's own colours, showing the palette as swatches, the accent's hex, and a small mock-up of the IDE wearing it — file tree, tabs, syntax-coloured code, status bar.
It saves to Downloads alongside your exports.
The card is for showing, not for installing — it contains no theme data. The picture is what you
post; the .json is what someone imports.
Note
Sharing is entirely file-based today. There is no gallery to upload to and no in-app browsing of other people's themes — you hand someone the file, or post the card.
The Assets tray#
Your library of images and colours, opened from the toolbar button tooltipped Assets tray.
Upload images there, or collect them out of the running UI with the inspector's Collect button. Save colours into it with the Swatch button under the toolbar's colour swatches. Clicking a saved colour loads it as your foreground; images are used from the background controls elsewhere, not from the tray itself.
The library is shared across every project on your machine, and it is not part of a theme export — a theme you send someone embeds the images it actually uses, but not your library.
Deleting an asset doesn't ask for confirmation either.