Archiving and Retiring Old Codex Themes: When to Clean House

Archiving Codex themes is the part of theming nobody plans for. You collect eight, then twenty, then a folder of half-finished experiments, and eventually reading the theme menu takes longer than a build takes to run. This is how I retire themes I no longer reach for, and what I check before deleting anything.

Two things make it worth doing. The menu is linear, so every dead entry costs you a scan of the whole list. And themes you liked once are not neutral: you reapply one out of nostalgia, decide it looks wrong, then spend four minutes getting back to where you were.

Which themes are ready to archive

The test is not whether a theme is good. Some of mine are perfectly fine and still got archived, because fine is not the same as chosen. What I actually ask is when I last applied it on purpose.

• No deliberate apply in two months, only accidental ones while scrolling the menu
• Three near-identical variants of one idea, and you cannot tell which is which
• Built for a monitor or a wallpaper you no longer have
• Kept only because making it cost you an evening

A codex theme cleanup workflow that fits in fifteen minutes

Fifteen minutes is enough. Going longer turns this into a project you keep postponing. Four passes, in order, and stop after the fourth.

• Pass 1: open the menu, mark anything you cannot describe from memory. Do not delete yet
• Pass 2: screenshot the ones you marked. A 200 KB png is cheaper than rebuilding a palette
• Pass 3: move marked themes out of the active themes directory into an archive folder
• Pass 4: restart Codex Skin Studio and check that the menu reads the way you expect

Pass 3 is the one people skip, and it is the whole point. Moving a theme out of the active folder is reversible in five seconds. Deleting it is not.

Retire an old codex theme or delete it: the difference

These get treated as one action and they are not the same. Retiring keeps the files somewhere you can reach and takes them out of the menu. Deleting removes them, and unless you exported first, the palette goes with them.

• Retire: folder moves to an archive directory, menu gets shorter, restore is a drag and drop
• Delete: files removed. Fine for themes you exported, painful for anything tuned by hand
• Export first: a theme.json plus the wallpaper is the whole theme, and that is what you back up
• Shared team themes: retiring one changes what everyone on the plan sees, so say so first

How often to run a cleanup

Twice a year suits most people, and tying it to something you already do stops it from sliding. I run mine when I change machines and when Codex ships a major update.

• After a machine migration, because half of what comes across is stuff you stopped using
• After a major Codex update, since you are reapplying themes anyway
• Never during a deadline week. Cleanup curiosity eats an hour you do not have

One thing I got wrong for a long time: I used to delete first and export later. It cost me a purple-on-black palette I had tuned over two evenings, and I have never reproduced it since.

FAQ

Where to go from here

Open the theme menu on codex-skin-studio.shop, count the entries you cannot describe from memory, and move those. Export before you delete anything, and the full export and restore steps sit at /en/blog/codex-theme-backup-and-restore. How often to switch at all is argued at /en/blog/how-often-should-you-switch-codex-themes. Everything else is at /en/blog.