Skip to content

Font Management

Deckyard includes a curated library of Google Fonts and lets you add custom fonts from multiple sources. Fonts are managed per organization and can be assigned to any theme.

Deckyard ships with 40 pre-selected Google Fonts across four categories:

CategoryExamples
Sans-serifInter, DM Sans, Plus Jakarta Sans, Nunito, Open Sans
SerifPlayfair Display, Lora, Merriweather, Source Serif 4
DisplayBricolage Grotesque, Fraunces, Sora, Space Grotesk
MonospaceJetBrains Mono, Source Code Pro, IBM Plex Mono

Curated fonts are available to all organizations without configuration. They are served locally from the server (no external requests), and are automatically embedded in exports.

When selecting fonts in the Theme Editor, curated fonts appear grouped by category in the font picker dropdown.

Organizations can add their own fonts from four sources. Custom font management requires the Designer role.

Add Font Family dialog with source options: Upload, Adobe Fonts, fonts.com, and Google Fonts

  1. Navigate to Settings > Fonts
  2. Click Add Font Family to create a new entry
  3. Choose a source type

Upload your own .woff2 or .woff font files directly.

  • Supported formats: .woff2 (recommended) and .woff
  • Maximum file size: 5 MB per file
  • Files are validated by format (magic byte check) — renaming a non-font file won’t bypass validation
  • Upload individual variants (weight + style combinations) after creating the family

Adding variants:

  1. Create the font family and select Upload as source
  2. In the variant grid, click Upload for the weight/style combination you need
  3. Select the font file
  4. Repeat for additional weights (e.g., Regular 400, Bold 700)

Connect fonts from your Adobe Fonts subscription.

  1. Select Adobe Fonts as source
  2. Enter your Typekit Project ID (found in your Adobe Fonts web project settings)
  3. Click Discover Fonts to see all fonts in the project
  4. Select the font family to import

Adobe Fonts load via an external stylesheet from use.typekit.net. The font is available as long as your Adobe subscription and web project remain active.

Connect fonts from your Monotype/fonts.com account.

  1. Select Monotype as source
  2. Enter your Project ID
  3. Optionally specify a version number
  4. Save the font family

Monotype fonts load via an external script from fast.fonts.net.

Add any Google Font — including fonts not in the curated library.

  1. Select Google Fonts as source
  2. Enter the font family name (e.g., Raleway)
  3. Optionally specify weights (e.g., 400,600,700). If omitted, defaults to 400, 600, and 700
  4. Save the font family

Google Fonts load via the Google Fonts CSS2 API.

Every font family is assigned a category: sans-serif, serif, display, or monospace. This determines:

  • How the font is grouped in the font picker
  • The CSS fallback stack (e.g., serif fonts fall back to serif, monospace to monospace)

When you delete a font family:

  • All associated variants and uploaded files are removed
  • Any themes referencing the font automatically fall back to their curated font setting
  • No presentations are broken — they just revert to the theme’s fallback font

Fonts are assigned to themes through the Theme Editor:

  1. Open a theme in the Theme Editor
  2. Use the Heading Font and Body Font dropdowns
  3. Both curated and custom fonts appear in the picker — custom fonts are listed in a separate “Custom Fonts” group
  4. Save the theme

Body fonts need both Regular (400) and Bold (700) weights to properly render slide content (paragraphs, lists, bold text). The font picker enforces this:

  • Uploaded fonts only appear in the body font picker if they have both weight 400 and 700 variants uploaded
  • Adobe, Monotype, and Google fonts are always available for body use, since their variant availability is managed externally

Heading fonts have no weight restriction — a single weight is fine for titles.

Fonts load differently depending on the context:

ContextUpload fontsAdobe / Monotype / Google fonts
Editor@font-face rules with file URLsExternal <link> or <script> tags
Embed views@font-face rules with file URLsExternal <link> or <script> tags
Published HTMLBase64-embedded @font-face (works offline)External <link> or <script> tags
PDF / PNG exportLoaded via network (Puppeteer)Loaded via network (Puppeteer)
  • Uploaded fonts are fully embedded in HTML exports as base64 data — exports work offline
  • External fonts (Adobe, Monotype, Google) require network access in exports. The external <link> and <script> tags are included, but the export won’t display correctly without internet
  • PDF and PNG exports always work because the server-side renderer (Puppeteer) has network access during generation
ActionRequired role
View available fontsAny user
Select fonts in Theme EditorAdmin
Add / edit / delete font familiesDesigner
Upload font variantsDesigner