Is a Codex skin free?

Yes. Designing and exporting a skin on GPT Skin costs nothing and needs no account. The browser builds the ZIP on your device; you only pay with your own time.

Do my images get uploaded?

No. The generator reads the selected image locally, keeps it in browser memory, and writes the download on the same device. There is no upload endpoint or server-side generation step.

Is a Codex skin an official OpenAI feature?

No. Skins come from community projects such as Fei-Away/Codex-Dream-Skin and from independent tools like this one. None of them are affiliated with or endorsed by OpenAI.

Does a Codex skin survive an app update?

Not automatically. A skin is an adapter layer on top of the desktop app, so a release that changes the window structure can break selectors. Restore the official appearance, then update the adapter before styling again.

Can I use my own photo or illustration?

Yes, as long as you own it or have permission to use and redistribute it. The image stays in the pack you export, so treat a shared skin the same way you would treat sharing the original file.

Codex Skin: What It Is and How to Make One (2026 Guide)

What a Codex skin actually changes

The short version: the app stays the app. A skin adds artwork and a color system around the real interface instead of swapping the window for a picture. Sidebar entries, the project switcher, task history, the composer, keyboard focus, and window resizing all remain native, because those are the parts you work in every minute — a theme that hides them is decoration, not a skin.

The visual layer usually covers the area behind task content, the home banner, suggestion cards, borders, and accent states. Readability is the constraint that decides whether a design survives contact with real work: diff views, terminal output, long approvals, and file names all sit on top of your image, so contrast has to come from a veil and a deliberate text color rather than from lucky cropping.

Sidebar, projects, tasks, and composer stay interactive.
Decoration never captures clicks or keyboard focus.
Text stays readable over the busiest part of the image.
The original appearance can be restored in one step.

What a skin does not do is change how Codex behaves. It is not a plugin, not a model setting, and not an official feature of the desktop app. It is a theme layer built on top of the running client, which is why compatibility has to be rechecked whenever the client updates. If you want the project history first, read what Codex Dream Skin is; the rest of this page is the practical path.

Three ways people get a Codex skin

The routes differ mainly in who maintains the adapter and how much of the work you can inspect before running anything.

1. Build it in the browser

The Codex skin generator on this site takes an image, applies a readability veil, blur, and interface text color, then shows the result inside a dense workspace specimen so you can judge contrast before installing. Exporting produces a ZIP with your artwork, theme.json, a README, and the community Dream Skin Studio runtime for macOS.

This route suits people who already know what they want the workspace to feel like. Everything happens locally: the file is read through your browser and the archive is assembled on your device.

2. Start from a community pack

Community releases ship a ready-made look together with their own install and restore scripts. Read the repository before you run them, check which app version the author tested, and prefer the upstream source over a re-uploaded archive from a social post. A theme installer is local code with access to your machine, so inspectability matters more than the screenshot.

3. Hand-write the CSS

Pasting a stylesheet into a running Electron app is the fastest way to make one screenshot look right and the slowest way to keep a theme working. Without a maintained adapter you own every selector change, every update, and every restore path yourself. It is a reasonable exercise for learning the structure; it is a poor long-term setup for daily work.

Start here

Build a Codex skin in three steps

1
Choose the artwork
Upload a PNG, JPG, or WebP you created or have permission to reuse, or start from one of the built-in moods. Wide images with a calm center leave the most room for task content.
2
Tune readability
Adjust the veil, blur, and interface text color while watching the live specimen. Check the sidebar, the composer, and the darkest and brightest parts of the image, not just the hero area.
3
Export and inspect
Download the ZIP, unzip the whole folder, read README.txt, and look at the bundled scripts before running Install My GPT Skin.command on macOS. Installation and restore are your decision, not something the download performs.

If you would rather compare directions before committing, browse the best GPT skin ideas for 2026 or the featured skins on the homepage. Both galleries are references only; your download always uses the image you choose.

Choosing an image that survives the workspace

Codex is not a wallpaper canvas. The reading column moves depending on what you open, so a subject that sits dead center will eventually end up behind code, a diff, or the composer. Put the interesting detail toward an edge, keep the center quiet, and assume the image will be cropped differently at a narrow window width than on a large monitor.

Contrast is the second filter. A photo with a bright sky or a white page behind the text column will fight every line of output unless the veil is heavy enough to flatten it — and a heavy veil wastes the image you picked. Test the design at two window sizes and in both a short task and a long scroll before exporting.

File hygiene matters too. Keep your source art somewhere stable and under a name you recognise; re-exports are normal, and a clean source file makes the second attempt five minutes instead of an afternoon.

What happens after a desktop app update

The desktop app's structure can change between releases. When it does, a theme that relied on the old structure will show up late, half-applied, or not at all, and the fix belongs in the adapter rather than in more specific CSS. Restore the official appearance first, confirm the app itself is healthy, then update the skin runtime and re-verify that sidebar, composer, and keyboard focus behave normally.

The same logic applies when the window looks right but feels wrong: if clicks land in the wrong place or tab order skips controls, stop using the themed session and restore. A skin is only worth keeping while it stays reversible. The symptom-first troubleshooting page walks through the common cases in the order worth trying them.

Codex skin FAQ

Is a Codex skin free?: Designing and exporting a skin here costs nothing and needs no account. The ZIP is built in your browser, so the only cost is your own time.
Do my images get uploaded?: No. The generator reads the file locally and writes the download on the same device. There is no upload endpoint and no cloud generation step.
Is this an official OpenAI feature?: No. Skins come from community projects and independent tools. This site is not affiliated with or endorsed by OpenAI, and the latest client compatibility of the bundled macOS adapter has not been verified in this release.
Does a skin survive an app update?: Not automatically. Restore the official appearance, then update the adapter and re-verify the interface instead of piling on CSS overrides.
Can I share the exported skin?: Yes, if you own the artwork or have permission to redistribute it. Share the ZIP and the installation source together so recipients can inspect both.

Keep going

Ready to experiment?

Turn your own image into a Codex skin.

Preview the theme behind a real workspace and export the pack locally — no account and no server upload.

Build a Codex skin