Reference
Themes
Give an artifact its own colors, fonts, and a cover, in the web app or over MCP. Every theme passes contrast checks, so every reader can read it.
What a theme changesLink to this section
A theme gives one artifact its own look. A long report can read like a printed page, and a team's documents can match its brand. Every theme passes WCAG AA contrast in light and dark, so every reader can read it.
A theme changes these parts:
- The colors of the content: text, cards, buttons, charts, code, diagrams, and tables.
- The page behind the artifact (the backdrop).
- The corner radius and the fonts.
The site header, the comments, and the controls keep the standard look, so readers always know where they are. The theme applies for every reader of the artifact.
A theme is a preset id, such as "paper", a team preset id, or theme JSON. An artifact with no theme of its own uses its team's default, or else the Default look. See Team themes. Every format can have a theme. A web page (html) sets its own colors and fonts inside its frame, so a theme changes the artifact's page around it, not the page in the frame.
Theme values never become raw CSS. The server checks each value and writes it again in one standard form. The page sets each value as a CSS custom property on the artifact's wrapper, and every card, chart, code block, diagram, and table inside reads it.
PresetsLink to this section
There are 8 presets. Each sample below uses the same theme engine as the artifact page, so you see what readers get. Copy an id and pass it as theme.
Default
defaultThe site's own look: warm paper and warm near-black, in Geist.
Geist Sans, code in Geist Mono
Paper
paperCream pages, sepia ink, and a sienna accent, in Work Sans.
Work Sans, code in Geist Mono
Graphite
graphiteCool neutral greys and slate, set in IBM Plex Sans and Plex Mono.
IBM Plex Sans, code in IBM Plex Mono
Ink
inkPure white and true black for the highest contrast, in Inter and JetBrains Mono.
Inter, code in JetBrains Mono
Ocean
oceanFaint sea-blue surfaces and a deep blue accent, in DM Sans.
DM Sans, code in Geist Mono
Forest
forestSoft sage surfaces and a moss accent, in Manrope.
Manrope, code in Geist Mono
Editorial
editorialA reading page: Instrument Serif headings over Source Serif 4 body text, with an oxblood accent.
Instrument Serif and Source Serif 4, code in Geist Mono
Classic
classicFamiliar and clear: Roboto with JetBrains Mono, cool greys, and a blue accent.
Roboto, code in JetBrains Mono
Set an artifact's themeLink to this section
People set a theme in the web app. Agents set it over MCP. Both save the theme the same way, as part of the artifact's history.
On the artifact pageLink to this section
If you can edit an artifact, you see Theme beside the icon above its title. On a computer, it shows when you point at the title. On a touch screen, it always shows. When the artifact has a theme, the button shows the theme's name.
Select it to open the presets as live samples, each with its name and fonts. Select a preset to apply it at once. Select Default to go back to the standard look. The arrow keys, Home, and End move between samples, and Enter or Space selects one.
When the artifact is shared with a team, the picker also shows that team's presets, under the team's name. When the team has a default, the first sample is Team default: it is selected while the artifact has no theme of its own, and selecting it removes the artifact's own theme. A private artifact offers the presets of every team you belong to.
The picker shows presets only. Agents can also set theme JSON over MCP. Then the picker tells you that the artifact has a custom theme, and a preset you select replaces it.
Readers do not see the control. They see only the theme.
Custom themesLink to this section
When an agent sets theme JSON on an artifact, the picker shows it first as Custom, with its swatch. Pick a preset to replace it. Two buttons sit above the swatches:
- Copy theme JSON copies the theme, ready to import as a team preset or to send to an agent.
- Save as team preset, for team owners and admins, opens the preset editor with the theme filled in. Give it a name and save; team members can pick it at once. The artifact keeps its own theme until someone picks the new preset.
For a new artifactLink to this section
New artifact opens a blank page, so you can start writing at once. It saves as soon as you write something. A new artifact uses Default. To pick another theme, open the artifact's page with Open and use the same picker in its header, which includes the presets of your teams.
Over MCPLink to this section
Agents set theme on artifacts_create or artifacts_update, on artifacts they can edit. The value is one of these:
- A preset id, such as
"paper". - A team preset id, such as
"team:acme-brand-x7k2p9". See Team themes over MCP. - Theme JSON, as described in Theme JSON.
nullor""on update, to remove the theme. The page goes back to the team default, or else the Default look.
Leave out theme to keep the current theme. artifacts_get and artifacts_list return the stored value: a preset id, theme JSON in its standard form, or null. artifacts_versions shows the theme of each version.
{
"name": "artifacts_create",
"arguments": {
"title": "Q3 launch plan",
"kind": "markdown",
"content": "# Q3 launch plan\n\n…",
"theme": "paper"
}
}{
"name": "artifacts_update",
"arguments": {
"id": "Vq3kJ0pXw2mZ8rT5yN1aBc",
"theme": {
"version": 1,
"mode": "auto",
"radius": "sm",
"fonts": {
"body": "inter",
"heading": "inter",
"mono": "jetbrains-mono"
},
"light": {
"background": "oklch(0.98 0.002 250)",
"foreground": "oklch(0.23 0.005 250)",
"mutedForeground": "oklch(0.48 0.01 250)",
"card": "oklch(1 0 0)",
"cardEdge": "oklch(0.23 0.005 250 / 0.1)",
"accent": "#0f766e",
"accentForeground": "#ffffff",
"chart": [
"#2a78d6",
"#df5d27",
"#009965",
"#be7500",
"#cc628c",
"#6250d6",
"#008300",
"#e34948"
]
},
"dark": {
"background": "oklch(0.17 0.004 250)",
"foreground": "oklch(0.94 0.003 250)",
"mutedForeground": "oklch(0.7 0.01 250)",
"card": "oklch(0.21 0.005 250)",
"cardEdge": "oklch(0.94 0.003 250 / 0.1)",
"accent": "#5eead4",
"accentForeground": "#042f2e",
"chart": [
"#3987e5",
"#d95926",
"#199e70",
"#c98500",
"#d55181",
"#9085e9",
"#0d880b",
"#e66767"
]
}
}
}
}{
"name": "artifacts_update",
"arguments": {
"id": "Vq3kJ0pXw2mZ8rT5yN1aBc",
"theme": null
}
}A theme that fails validation stops the whole call: nothing is saved. The error lists every problem, and for low contrast it gives colors that pass. See Suggested colors. Agents cannot make or change presets.
themes_listLink to this section
themes_list returns each preset with its id, name, look, mode, and fonts, then, under teams, the presets and default of each team you belong to. It also returns the font ids that theme JSON can use in each slot. It saves nothing, and read-only connections can use it. See the MCP reference.
{
"presets": [
{
"id": "default",
"name": "Default",
"description": "The site's own look: warm paper and warm near-black, in Geist.",
"mode": "auto",
"fonts": {
"body": {
"id": "geist-sans",
"family": "Geist Sans"
},
"heading": {
"id": "geist-sans",
"family": "Geist Sans"
},
"mono": {
"id": "geist-mono",
"family": "Geist Mono"
}
}
},
{
"id": "paper",
"name": "Paper",
"description": "Cream pages, sepia ink, and a sienna accent, in Work Sans.",
"mode": "auto",
"fonts": {
"body": {
"id": "work-sans",
"family": "Work Sans"
},
"heading": {
"id": "work-sans",
"family": "Work Sans"
},
"mono": {
"id": "geist-mono",
"family": "Geist Mono"
}
}
},
"…6 more"
],
"teams": [
{
"team": "acme",
"name": "Acme",
"default": {
"id": "team:acme-brand-x7k2p9",
"name": "Acme brand"
},
"presets": [
{
"id": "team:acme-brand-x7k2p9",
"name": "Acme brand",
"description": "Our colors and Inter.",
"mode": "auto",
"fonts": {
"body": {
"id": "inter",
"family": "Inter"
},
"heading": {
"id": "inter",
"family": "Inter"
},
"mono": {
"id": "geist-mono",
"family": "Geist Mono"
}
}
}
]
}
],
"customFonts": {
"body": [
"geist-sans",
"inter",
"roboto",
"work-sans",
"dm-sans",
"manrope",
"ibm-plex-sans",
"source-serif-4"
],
"heading": [
"geist-sans",
"inter",
"roboto",
"work-sans",
"dm-sans",
"manrope",
"ibm-plex-sans",
"source-serif-4",
"instrument-serif",
"fraunces"
],
"mono": [
"geist-mono",
"jetbrains-mono",
"ibm-plex-mono"
]
},
"usage": "Set `theme` on artifacts_create or artifacts_update to a preset id, or to theme JSON (fonts by id from customFonts). A team preset id (\"team:…\") works on artifacts shared through that team, and on your private artifacts when you belong to the team. An artifact with no theme uses its team's default, then the site default. Pass null to remove it. Team presets and defaults are set by team owners and admins in team settings, never over MCP. Rules and an example: /docs/themes.",
"covers": {
"gradients": [
{
"id": "stone",
"name": "Stone"
},
{
"id": "mist",
"name": "Mist"
},
{
"id": "tide",
"name": "Tide"
},
{
"id": "meadow",
"name": "Meadow"
},
{
"id": "dawn",
"name": "Dawn"
},
{
"id": "ember",
"name": "Ember"
},
{
"id": "bloom",
"name": "Bloom"
},
{
"id": "dusk",
"name": "Dusk"
}
],
"usage": "Set `cover` on artifacts_create or artifacts_update to a gradient id (it follows the theme and light or dark mode), or to \"file:<file id>\" for an uploaded PNG, JPEG, GIF, WebP, or AVIF of at most 2 MB, with an optional `coverPosition` (0 top to 100 bottom). Pass null to remove it. More: /docs/themes#covers."
}
}History and approvalLink to this section
A theme change is saved as a new version, like a title or icon change. History shows it, and Restore brings an older theme back.
On a link or public artifact shared through a team, a theme change by a member or an agent waits for a team owner or admin to approve it, like a title change. Until then, readers outside the team see the approved theme. Owners and admins see the old and new theme names on the team page. Agents never approve. See Edits to shared artifacts.
Team themesLink to this section
A team can give its artifacts one look. Team owners and admins keep the team's own presets and pick a team default on the team page, under Themes. Everyone in the team can see them and use the presets. People outside the team never see the list; they see only how an artifact looks.
Which theme showsLink to this section
The first match wins:
- The artifact's own theme: a preset, a team preset, or theme JSON.
- The default of the team the artifact is shared through (team, link, or public in a shared team).
- The Default look.
Private artifacts, and artifacts shared through a personal team, have no team default. Every reader sees the same theme, signed in or not: a public page in a team with a default shows that default to everyone.
Team presetsLink to this section
Owners and admins create, edit, duplicate, and delete presets. The editor has a form for every theme field (colors for light and dark, chart colors, fonts from the allowlist, radius, and mode) and a JSON tab with the same theme JSON agents use. A live preview draws a sample artifact and cover with the real theme, in light or dark. Start a new preset from any built-in or team preset.
A preset must pass the same validation and contrast checks as any theme. Text that fails contrast is marked at its field with a suggested color that passes, and Apply suggestions sets them all.
A team preset id looks like team:acme-brand-x7k2p9 and never changes, even when the preset is renamed. Artifacts store this id, not a copy, so an edit to the preset shows on every artifact that uses it at once, with no new versions and no approval. Versions store the id too.
Before you delete a preset, the team page says how many artifacts use it. They fall back to the team default, then the Default look. If it was the team default, the team goes back to the Default look. An artifact that moves to another team, or that names another team's preset, falls back the same way.
A team can keep up to 50 presets.
Import and exportLink to this section
The preset editor can move a theme in and out as JSON, the same theme JSON agents use:
- Copy JSON and Download JSON export the preset once it is valid. Send it to an agent, keep it in a repository, or import it in another team.
- Import JSON takes pasted JSON or a
.jsonfile and replaces the editor's theme. It runs the same checks as a save. JSON with unknown keys or colors that do not parse is refused with every problem named. A theme that fails only contrast loads, with the suggested colors marked and Apply suggestions ready; it saves once it passes.
The team defaultLink to this section
Owners and admins pick a built-in preset or a team preset as the team default, or Site default for none. It is a team setting: it files no artifact versions and needs no approval. The team page shows who changed it last and when, and the server logs each change.
Every save of a preset and every change of the team default is kept: owners and admins open History in the preset editor, or Team default history on the team page, and Restore saves that earlier theme again as a new change. Old entries never change, the last 50 are kept, and an old theme that fails today's checks opens in the editor with suggested colors instead.
Team themes over MCPLink to this section
themes_list returns the presets and default of each team you belong to, never another team's. Pass a team preset id as theme on an artifact shared through that team, or on a private artifact when you belong to the team. Any other team preset id is refused, and nothing is saved. artifacts_get returns a team preset id only to the author and the team; other readers get "custom" in its place.
Agents use team presets but never create, change, or delete them, and never change the team default. Those stay with the team's owners and admins.
CoversLink to this section
A cover is a banner across the top of the artifact page, like a book jacket: it makes an artifact easy to know at a glance. It is about 240 px tall on a computer and 160 px on a phone, and the artifact icon sits across its lower edge.
A cover is a gradient id, such as "mist", or an image you upload. Every format can have a cover. An artifact with no cover shows none.
GradientsLink to this section
Gradients are soft tints of the artifact's own theme colors, so a cover always matches the theme, in light and in dark. Each sample shows light and dark in the Default look (top row) and in Ocean (bottom row). Copy an id and pass it as cover.
Stone
stoneMist
mistTide
tideMeadow
meadowDawn
dawnEmber
emberBloom
bloomDusk
dusk
Add a cover on the pageLink to this section
If you can edit an artifact, you see Add cover beside the icon and theme above its title. It adds a gradient at once. Point at the cover (or tap it on a touch screen) to see its controls:
- Change cover opens the gradients and Upload an image. Any photo works, straight from your phone: your browser turns it upright, resizes it to at most 2400 px, saves it as a JPEG under 2 MB, and removes its camera data, such as the location. A PNG with transparency stays a PNG when it already fits. Browsers that cannot open HEIC photos say so; save the photo as a JPEG first.
- Image icons get the same care: in the icon picker's Upload tab, any photo works, resized to at most 512 px and saved under 1 MB without its camera data. A transparent logo stays a PNG, and a GIF that already fits uploads as is.
- Reposition, for images, lets you drag the image up or down. You can also use the arrow keys (Shift for bigger steps), Home, and End. Enter or Save position saves; Escape or Cancel stops.
- Remove takes the cover away at once. Restore brings it back (see History and approval).
A new artifact starts without a cover. Add one on its page once you have written something. Readers see only the cover.
Covers over MCPLink to this section
Agents set cover on artifacts_create or artifacts_update, on artifacts they can edit. The value is a gradient id, "file:<file id>" for an uploaded image, or null or "" on update to remove it. coverPosition (0 to 100) sets an image's focal point; sent alone, it moves the current image cover. Leave both out to keep the cover.
themes_list lists the gradients. artifacts_get, artifacts_list, and artifacts_versions return cover and coverPosition. A cover that breaks a rule stops the whole call, and nothing is saved.
{
"name": "artifacts_create",
"arguments": {
"title": "Q3 launch plan",
"kind": "markdown",
"content": "# Q3 launch plan\n\n…",
"theme": "paper",
"cover": "dawn"
}
}{
"name": "artifacts_update",
"arguments": {
"id": "Vq3kJ0pXw2mZ8rT5yN1aBc",
"cover": "file:0f8fad5b-d9cb-469f-a165-70867728950e",
"coverPosition": 30
}
}{
"name": "artifacts_update",
"arguments": {
"id": "Vq3kJ0pXw2mZ8rT5yN1aBc",
"coverPosition": 60
}
}{
"name": "artifacts_update",
"arguments": {
"id": "Vq3kJ0pXw2mZ8rT5yN1aBc",
"cover": null
}
}Cover imagesLink to this section
Upload the image like any file (files_request_upload, then PUT, then files_finalize), and pass its id. The save attaches it to the artifact. Only people who can read the artifact can load the image.
| Rule | Value |
|---|---|
| Types | PNG, JPEG, GIF, WebP, or AVIF. SVG is refused, because it can carry script. |
| Size | At most 2 MB. A bigger file is refused with an error, and nothing is saved. Wide images look best; about 2400 px wide is plenty. |
| Link previews | Draw only JPEG and PNG covers of at most 2 MB. Agents: resize and save as JPEG before you upload. In the web app, Upload an image does this for you. |
| Owner | Your own finished upload, or a file already attached to this artifact. A file attached to another artifact is refused. |
| Source | Uploads only. Remote URLs are refused. |
| coverPosition | 0 (top) to 100 (bottom). 50, the centre, is the default. |
| Stored value | At most 64 characters, such as "mist" or "file:<id>@30". |
Cover history and approvalLink to this section
A cover change, including a new focal point, is saved as a new version. History shows it, and Restore brings an older cover back, image included: an uploaded cover image is kept while any version in the history shows it, and deleted when the last such version leaves the history (after 100 newer versions or a year) or when the artifact is deleted. If you deleted the image file yourself, Restore leaves the artifact without a cover. Readers outside the team can open only the approved version's cover image.
On a link or public artifact shared through a team, a cover change by a member or an agent waits for a team owner or admin to approve it. Until then, readers outside the team see the approved cover. Agents never approve.
Outside the pageLink to this section
The theme also shows where the artifact appears away from its page.
MarkdownLink to this section
The Markdown version of an artifact (/artifact/<id>.md) names the theme it shows in the header, as - Theme: Paper, - Theme: Custom for theme JSON, or - Theme: Acme brand (team default) when it shows its team's default. An artifact that shows the Default look has no Theme line. Team preset names are the team's own: readers outside the team see - Theme: Custom instead, never the name, and never "team default". Built-in names show to everyone. A cover shows as - Cover: Mist, or - Cover: Image, never with a link to the file. See Read artifacts without MCP.
Link previewsLink to this section
The link preview card of a link or public artifact uses the light palette of the theme the approved version shows: its own, or else the team default. The text on the card stays in Geist, because preview images cannot use the theme fonts. The image link names the approved version and the theme, so a new team default or a preset edit gives the card a fresh link, and sites that keep old cards show the new one.
A cover becomes the card's background. A gradient is drawn in the theme's light palette, with dark text. A PNG or JPEG image of at most 2 MB is drawn under a dark shade, with light text. Preview images cannot draw WebP, GIF, or AVIF, so those covers keep the standard background there. Images uploaded in the web app are always JPEG or PNG.
Theme JSONLink to this section
Theme JSON is an object with these keys. Unknown keys are refused at every level.
| Key | Value | Rule |
|---|---|---|
| version | 1 | Required. Always 1. |
| light | palette | Required. The colors for light mode. See Colors. |
| dark | palette | Required. The colors for dark mode, with the same keys. |
| radius | "none" | "sm" | "md" | "lg" | "xl" | Optional. Corner size. Default "md". |
| fonts | { body, heading, mono } | Optional. Font ids by slot. Each slot left out uses Geist Sans or Geist Mono. |
| mode | "auto" | "light" | "dark" | Optional. Locks light or dark. Default "auto". |
ColorsLink to this section
Each palette has these keys. Colors can be hex (#1d4ed8), rgb(), hsl(), or oklch(), and are stored as oklch(). Quieter surfaces (muted fills, borders, the code background, and diagram lines) are mixed from these colors. Code syntax colors keep their hues but change in lightness until they are clear on the code background.
| Key | Sets | Used for |
|---|---|---|
| background | --background | The page behind the artifact (the backdrop). |
| foreground | --foreground, --card-foreground | Body text and headings. |
| mutedForeground | --muted-foreground | Secondary text: captions, labels, table heads. |
| card | --card, --popover | Cards, panels, and frames on the page. |
| cardEdge | --card-edge, --code-border | The hairline edge of a card. It can be transparent, such as oklch(0.2 0 0 / 0.09). |
| accent | --primary | Primary buttons and the strongest marks. |
| accentForeground | --primary-foreground | Text on the accent. |
| chart | --series-1 … --series-8 | 6 to 8 chart colors, in order. A shorter palette repeats. A color too faint to show at 3:1 on a surface is drawn darker or lighter, with the same hue. |
RadiusLink to this section
| radius | --radius | Cards |
|---|---|---|
| none | 0rem | 0rem × 1.4 |
| sm | 0.25rem | 0.25rem × 1.4 |
| md | 0.375rem | 0.375rem × 1.4 (the default) |
| lg | 0.5rem | 0.5rem × 1.4 |
| xl | 0.625rem | 0.625rem × 1.4 |
FontsLink to this section
A theme sets a body, a heading, and a mono font by id. Display faces are for headings only, and mono faces are for code only. The size is the upright latin file that a reader downloads.
| Id | Font | Slots | Size |
|---|---|---|---|
| geist-sans | Geist Sans | Body, Headings | Always loaded |
| inter | Inter | Body, Headings | 47.3 KB |
| roboto | Roboto | Body, Headings | 36.6 KB |
| work-sans | Work Sans | Body, Headings | 49.3 KB |
| dm-sans | DM Sans | Body, Headings | 36.1 KB |
| manrope | Manrope | Body, Headings | 23.9 KB |
| ibm-plex-sans | IBM Plex Sans | Body, Headings | 39.3 KB |
| source-serif-4 | Source Serif 4 | Body, Headings | 49.8 KB |
| instrument-serif | Instrument Serif | Headings | 14.7 KB |
| fraunces | Fraunces | Headings | 35.7 KB |
| geist-mono | Geist Mono | Code | Always loaded |
| jetbrains-mono | JetBrains Mono | Code | 39.5 KB |
| ibm-plex-mono | IBM Plex Mono | Code | 9.8 KB |
Light, dark, and mode locksLink to this section
Readers keep their own light or dark choice, so every theme has both palettes. Set mode to lock one: "auto", "light", "dark". The default is "auto", which follows the reader.
Size limitsLink to this section
| Limit | Value |
|---|---|
| Theme JSON | 8,000 characters, as JSON text. A full theme is about 1,500. |
| Preset id | 64 characters. |
| One color | 64 characters. |
| chart | 6 to 8 colors in each palette. |
| Problems listed | The first 12, then a count of the rest. |
ValidationLink to this section
- Known keys only, at every level.
versionmust be1. - Colors must be hex,
rgb(),hsl(), oroklch(), with channels in range. Named colors,url(),var(),expression(), comments, braces, and;are refused. - Only
cardEdgecan be transparent. Every other color must be opaque, so its contrast can be measured. - In the light palette, the background and the card need an oklch lightness of at least 0.7. In the dark palette, they need at most 0.4.
- Fonts must come from the list above and suit their slot.
- Each problem comes back with the path of the bad value, such as
dark.mutedForegroundorfonts.body.
ContrastLink to this section
Every theme must pass WCAG AA contrast in both palettes. A theme that fails is refused. It is never changed without notice. The message names the pair and its ratio.
| Text | On | Minimum | Why |
|---|---|---|---|
| foreground | background | 4.5:1 | body text on the page |
| foreground | card | 4.5:1 | body text on cards |
| mutedForeground | card | 4.5:1 | secondary text on cards |
| mutedForeground | background | 4.5:1 | secondary text on the page |
| accent | card | 3:1 | buttons and controls on cards |
| accentForeground | accent | 4.5:1 | labels on accent buttons |
Code colors
Status colors
Focus ring
Suggested colorsLink to this section
When contrast fails, the error also gives the nearest passing color for each failing text color. The fix moves only the lightness of the text colors and the accent, away from their surface. It never changes a background or a card. Use the suggested colors as given, and the theme passes.
This is the real error for the Classic preset with secondary text that is too faint in both palettes:
The theme is not valid:
- light.mutedForeground: light.mutedForeground on light.card is 2.53:1; secondary text on cards needs at least 4.5:1 (WCAG AA).
- light.mutedForeground: light.mutedForeground on light.background is 2.39:1; secondary text on the page needs at least 4.5:1 (WCAG AA).
- dark.mutedForeground: dark.mutedForeground on dark.card is 2.34:1; secondary text on cards needs at least 4.5:1 (WCAG AA).
- dark.mutedForeground: dark.mutedForeground on dark.background is 2.52:1; secondary text on the page needs at least 4.5:1 (WCAG AA).
Nearest passing colors (autofix):
- set light.mutedForeground to oklch(0.5487 0.0192 261.32)
- set dark.mutedForeground to oklch(0.6061 0.0263 256.8)
Fix these and save again, or pass a preset id instead (themes_list). Rules: /docs/themes#validation and /docs/themes#contrast.A full themeLink to this section
The Classic preset as theme JSON. Leave out radius, fonts, or mode to use the defaults: "md", Geist and Geist Mono, and "auto".
{
"version": 1,
"radius": "lg",
"fonts": {
"body": "roboto",
"heading": "roboto",
"mono": "jetbrains-mono"
},
"light": {
"background": "oklch(0.98 0.002 250)",
"foreground": "oklch(0.23 0.005 250)",
"mutedForeground": "oklch(0.48 0.01 250)",
"card": "oklch(1 0 0)",
"cardEdge": "oklch(0.23 0.005 250 / 0.1)",
"accent": "oklch(0.5 0.15 255)",
"accentForeground": "oklch(0.99 0 0)",
"chart": [
"#2a78d6",
"#df5d27",
"#009965",
"#be7500",
"#cc628c",
"#6250d6",
"#008300",
"#e34948"
]
},
"dark": {
"background": "oklch(0.17 0.004 250)",
"foreground": "oklch(0.94 0.003 250)",
"mutedForeground": "oklch(0.7 0.01 250)",
"card": "oklch(0.21 0.005 250)",
"cardEdge": "oklch(0.94 0.003 250 / 0.1)",
"accent": "oklch(0.73 0.12 255)",
"accentForeground": "oklch(0.17 0.004 250)",
"chart": [
"#3987e5",
"#d95926",
"#199e70",
"#c98500",
"#d55181",
"#9085e9",
"#0d880b",
"#e66767"
]
},
"mode": "auto"
}How fonts loadLink to this section
A page loads only the fonts of the theme it shows. A page with no theme loads only Geist, the site font. The picker loads each preset's fonts only while it is open, and the samples on this page load their fonts when you scroll to them.
Every theme font except Geist comes from Google Fonts under the SIL Open Font License. The files are stored in the repository under public/fonts/v1/<id>/: the latin woff2 files, a small font.css, and the font's license. Readers' browsers never get a font from another site.