Skip to content
Codex DesignBETA

Codex for designers.

Codex started as a coding agent, but OpenAI says non-developers, designers among them, are now its fastest-growing users. You do not need to code to use it: you describe what you want, look at what it builds, and point at what to change. This guide covers what Codex is good at for design work, a setup that fits a designer, a first session you can follow, and where it still falls short.

Updated November 8, 2026 · 8 min read

The short answer

  • Yes, designers use Codex. OpenAI says non-developers, designers among them, make up about 20% of Codex users and are growing more than three times as fast as developers.
  • You work by describing and pointing. Codex builds real, clickable screens in HTML or your product’s code. You review them in a browser and point at what to change.
  • A good setup: the Codex app, the Figma plugin, OpenAI’s Product Design plugin, and a DESIGN.md with your design system. Add a canvas if you want to compare many screens side by side.
  • It is not a vector tool. Codex makes working UI, not Figma frames by default. For pixel work on the canvas, Figma is still the place; Codex can send pages back to it.

What designers use Codex for

TaskWhat Codex does
Explore directionsBuilds several takes on the same screen with your real content, so you can compare
PrototypeTurns a brief, a mockup, or a Figma frame into a clickable prototype
Design from a live productRecreates a page you own as an editable copy, then tries changes on it
Audit a flowWalks through a flow, takes screenshots, and lists UX and accessibility issues
Keep code and design in syncCompares Figma variables with the tokens in code and lists the differences
Ship small UI fixesChanges spacing, copy, or colors in the product code and prepares the change for review

The last one is new for many designers: with access to the repository, you can fix the button padding yourself instead of filing a ticket, and a developer reviews the change.

A setup that fits a designer

  1. Install the Codex app. It is part of the ChatGPT desktop app on Mac, Windows, and Linux. Codex is included in every ChatGPT plan; image generation and regular use need Plus or above. See how to install Codex and Codex pricing.
  2. Connect Figma. In the Codex app, open Plugins, click + next to Figma, and allow access. Codex can then read frames, components, and variables, and write back to the canvas. Details and fixes: how to use Figma with Codex.
  3. Install the Product Design plugin. OpenAI’s own plugin for design work: it confirms the brief, shows three directions, builds a prototype, audits flows, and shares prototypes. See the Codex Product Design plugin.
  4. Write down your design system. Put colors, type, spacing, radius, and component rules in a DESIGN.md file in your project, so every screen Codex makes follows them. See DESIGN.md for Codex, or start from one of our free design systems.
  5. Optional: add a canvas. If you want many screens and directions side by side as live pages, with visual editing of fonts, colors, and spacing, add Codex Design.

Your first session

A good first project is one real screen you already know well, such as a settings page or an onboarding step.

  1. Open a project folder. For a new idea, make an empty folder and open it in Codex. For an existing product, open its repository and ask a developer to point you at where the UI lives.
  2. Brief it like a designer. Who is it for, what is the one job of the screen, what content goes on it, and what to avoid. A vague brief gets generic results.
  3. Ask for three directions first. Not one. Seeing options is faster than describing a style in words.
  4. Pick, then refine by pointing. Open the result in the Codex in-app browser and use Annotations to point at an element: leave a comment or change a CSS value, then send it back.
  5. Check it like you would check any design. Look at mobile width, empty and error states, contrast, and long text. Ask Codex to show each state.
First brief
I'm a product designer. Design the notification settings screen for a project management app used by small agency teams.
The one job of this screen: let people choose which events notify them, and how (email, push, or none), without reading a manual.
Use the content below as real data, not lorem ipsum: [paste your list of events].
Follow DESIGN.md. Show me three directions that differ on purpose (dense and table-like, calm with grouped cards, and a guided version with presets), as separate pages I can open side by side. Don't build anything else yet.
Review the states
For the direction I picked, show me these states as separate pages: first-time user with nothing set, everything turned off, an error saving, and the screen at 375px wide with the longest event names. List anything that breaks.

Prompts for everyday design work

Figma frame to prototype
Build this Figma frame as a clickable prototype: [link to one frame]. Use the variables from Figma for colors and spacing. Make the tabs and the primary button work, and show the loading state after the button is pressed.
Accessibility pass
Check this page for accessibility: color contrast of every text and icon against WCAG AA, focus order and visible focus, touch targets under 44px, and images without alt text. Show each issue with a screenshot and the fix, then apply the fixes I approve.
Small UI fix in the product
On the pricing page, the cards have uneven padding and the "Most popular" badge overlaps the title on mobile. Fix both using our existing spacing tokens, change nothing else, and show me before and after screenshots at 375px and 1280px.

What Codex is not good at yet

  • Taste by default. Left alone, Codex reaches for the same safe choices as other models: violet gradients, glass cards, emoji icons, Inter everywhere. A design system and three directions fix most of it; our list of AI UI design tells covers the rest.
  • Vector and illustration work. It builds UI in code. Icons, illustrations, and brand graphics are better made in a design tool or with image generation, then placed in.
  • Knowing your product. It only knows what you tell it and what is in the files it can see. Save product context once (the Product Design plugin offers to) and keep DESIGN.md up to date.
  • Limits. Codex usage counts against your ChatGPT plan, and image generation uses it faster. Long explorations are cheaper as HTML than as many generated images.

Codex or Claude Code for designers?

Both can build and refine UI, read Figma through Figma’s MCP server, and follow a DESIGN.md. Codex has OpenAI’s Product Design plugin, image generation in the same agent, and annotations in its in-app browser. Claude Code has Claude Design built in through /design, and its desktop app can preview your running app. Many teams use both. See Codex vs Claude Code for UI design for a closer look.

Frequently asked questions

Do I need to know how to code to use Codex?

No. You describe the screen, review it in the browser, and point at changes. Some comfort with folders and reading a page’s structure helps, and working inside a product’s repository goes better with a developer nearby for the first session.

Which ChatGPT plan do designers need?

Codex is in every plan, including Free, but Free has no image generation and is meant for quick tasks. For regular design work, Plus or above. See Codex pricing.

Can Codex replace Figma?

Not for most teams. Codex is strongest at turning ideas and designs into working screens and checking them. Figma is still where teams lay out, comment, and keep the design library. The Figma plugin lets the two pass work back and forth.

Keep reading

An independent plugin for Codex. Not affiliated with or endorsed by OpenAI.