Original Codex skins · local themes · no sign-up

Codex skins that look good and work.

Explore original Codex skin directions, learn how a readable local theme works, then make your own when you are ready. No artwork is uploaded.

0 image uploadsWCAG contrast checksReview-first data-only export
Codex · Graphite TerminalLIVE

Graphite Terminal · live concept

A calmer place to build.Native controls stay visible. The background sets the mood.
Ask Codex to build, review or explain…
3Codex surfaces previewed
7Inspectable recipe files
0Private images sent to us

Four deliberate steps

How to make a Codex skin safely

A good skin is not just a striking background. It needs a calm reading area, tested contrast, an understandable package, and a restore plan.

  1. 01

    Choose rights-cleared art

    Use your own image or artwork you are licensed to use. Wide images around 2000 pixels or more give the builder room to crop.

  2. 02

    Frame around the interface

    Move the focal point away from the sidebar and reading column, then adjust dimming, blur, and panel opacity.

  3. 03

    Test Home, Task, and Diff

    Check a quiet home state, an active task, and dense code changes. Passing one screen is not enough.

  4. 04

    Export, review, then install

    Inspect the manifest, images, tokens, and hashes. Use a reviewed local engine and practice its verification and restore path.

Information, not hype

What this Codex skin maker adds

Most theme screenshots show only the final mood. This builder helps you make decisions that survive real work.

Composition that matches export

The same crop controls drive the live workspace and the packaged WebP background.

Contrast measured in the browser

Text and accent colors are checked against WCAG ratios before you download anything.

Data-only package anatomy

The recipe separates its manifest, theme settings, background, preview, license note, and SHA-256 checksums.

Honest platform boundaries

The site does not claim that a browser ZIP can safely install itself into the official Codex desktop app.

Installation reality

One design, different platform paths.

Codex Skin Maker prepares the visual recipe. The upstream Dream Skin project owns local launch, injection, verification, and recovery behavior.

No injector

Color tokens only

Use the copied colors as a reference for supported appearance settings. Background images require a separate skin engine.

  • No local debug session
  • Fastest recovery
  • Background image not included
macOS

Dream Skin Studio

The upstream macOS flow supports user-image customization, installation to a stable user path, verification, and restore.

  • User image supported upstream
  • Official app validation
  • Start, verify, and restore entries
Windows

Dream Skin scripts

The upstream Windows flow installs, launches, verifies, repairs, and restores a decorative skin without modifying WindowsApps.

  • PowerShell workflow
  • Screenshot verification
  • User-image parity may differ

Privacy by construction

Your artwork does not need a server round trip.

File selection, decoding, crop preview, color checks, WebP rendering, PNG preview, hashing, and ZIP creation happen locally in your browser.

Your image
Your browser
Your recipe

The site can still load normal page analytics when configured, but the selected artwork is not sent to our server for building or export.

Clear answers

Codex skin maker FAQ

The important questions about privacy, installation, compatibility, artwork rights, exports, and the unofficial Dream Skin workflow.

A Codex skin is an unofficial visual layer for the Codex desktop app. In the Dream Skin approach, a local engine launches Codex with a loopback debugging session and applies CSS and decorative elements while native controls remain interactive.

No. The selected image is decoded, previewed, cropped, encoded, hashed, and packaged in your browser. It is not uploaded to our server for these operations.

No. The ZIP is a reviewable data package, not an executable installer. Use a Dream Skin engine you trust, and follow its platform-specific install, verify, and restore documentation.

The website does not modify Codex. The referenced open-source Dream Skin project says its approach avoids editing the official app bundle, app.asar, WindowsApps, or code signature and instead uses local CDP injection.

The builder accepts JPEG, PNG, WebP, and AVIF up to 20 MB when your browser can decode them. PNG, JPEG, or WebP are the safest fallback choices for broad browser support.

A theme can look good in a screenshot and still make task text, controls, or diffs hard to read. The builder checks normal text against 4.5:1 and accent controls against 3:1.

The recipe structure is reusable, but you need rights to the background image, people, characters, logos, and brands you include. Personal use does not automatically grant redistribution rights.

No. Codex Skin Maker is independent and unofficial. OpenAI and Codex names and trademarks belong to their respective owners.

Start with one image

Make the mood useful, not distracting.

Build a readable Codex skin, inspect the recipe, and keep a restore path before you apply it.

Open Codex Skin Maker