Load Google, Adobe, or self-hosted fonts

Pro

Slides includes a number of preset font options but we also allow you to use custom fonts from Typekit, Google Fonts or even your own host.

Using fonts from Google

Follow these instructions to load a Google Font and apply it to your presentation.

  1. Open the CSS editor.

  2. Select the Custom fonts button, represented by a T in the upper-right corner.

    Custom fonts button in the upper-right corner of the CSS editor

  3. Enter the Google Font families you want to load. Slides suggests matching fonts as you type. Select Save when you are finished.

    Load custom fonts dialog with Lobster entered as a Google Font

  4. Select Apply custom font above the CSS editor, then choose the font you want to use.

    Apply custom font menu with Lobster available to select

  5. Choose where to apply the font: Body text, Heading 1, Heading 2, or Heading 3. You can select more than one option. Select Apply to add the required CSS.

    Options for applying the Lobster font to body text or heading levels

The generated CSS appears in the editor and the presentation preview updates to show the result.

Lobster applied to the presentation heading with its CSS visible in the editor

Here's an example where a custom font called "Lobster" is applied to all headings and "Open Sans" is used for body text:

// Use the "Lobster" font for all headings
.slides h1,
.slides h2,
.slides h3 {
    font-family: "Lobster";
}

// Use "Open Sans" for body text
.slides {
    font-family: "Open Sans";
}

Using fonts from Typekit/Adobe Fonts

  1. Add your font in Adobe Fonts/Typekit.

    Font selected in Adobe Fonts

  2. Create a new Typekit web project.

    Creating an Adobe Fonts web project

  3. Copy the Typekit ID from inside the embed code.

    Adobe Fonts project ID

  4. Add the Typekit ID to the Custom Fonts popup in the Slides editor.

    Adobe Fonts project ID field in Slides

  5. Apply the font with CSS. Use the font name exactly as shown in step 3.

    Adobe font-family name used in CSS

Typekit domain

If you're loading Typekit fonts make sure that your kit is configured to allow loading from the slides.com and *.slides.com domains.

Typekit font names

If you're loading fonts from Typekit you'll need to open the kit configuration on the Typekit site to locate your font name(s). These names aren't always predictable – for example, if you're using Fira Sans the name may be something like "fira-sans-2". You can learn more about how to locate your Typekit CSS font names in the following article: https://blog.typekit.com/2011/06/29/using-typekit-fonts-in-your-own-css/

Using fonts from another host

You can load custom font files directly from another domain.

  1. Open the CSS editor

  2. Define your font using @font-face and apply it to the content, for example:

// Include a custom font
@font-face {
  font-family: "Cabin Sketch";
  src: url("https://static.slid.es/fonts/cabinsketch/cabinsketch-regular.woff") format("woff"),
       url("https://static.slid.es/fonts/cabinsketch/cabinsketch-regular.ttf") format("truetype");
}

.slides h1, .slides h2, .slides h3 {
    font-family: "Cabin Sketch";
}

Server requirements

Externally hosted font files must be served over HTTPS.

The server must also be configured to allow the files to be loaded from the slides.com and *.slides.com domains. Cross domain loading is prevented by default by a mechanism called "Cross-Origin Resource Sharing" (CORS). To learn more about CORS and how to configure it please see this article: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

Applying fonts with CSS

When applying custom fonts or other CSS, make your selectors specific enough to override the default Slides styles. The easiest approach is to prefix the selector with .slides:

// Apply font to headings
.slides h1, .slides h2, .slides h3 {
  font-family: "My Custom Font";
}

// Apply font to body text
.slides {
  font-family: "My Custom Font";
}

// Apply font to links
.slides a {
  font-family: "My Custom Font";
}

Presenting offline

Custom fonts loaded from a third-party server do not work in offline ZIP or Dropbox exports. They are included when exporting to PDF.