Theming and branding
Set a course's theme (presets, colors and fonts) and your organization's branding (name, logo, color, export footer), and where each one shows: the preview, the hosted player and exported packages.
Last updated 4 min read
A course's theme
In the course editor, open More → Theme. The Theme editor has:
- Presets: Corporate (the default), Modern, Warm, Bold, Academic, Minimal, Playful and Dark Mode.
- Colors: Primary, Accent, Background and Text.
- Fonts: a body font (Inter, Roboto, Lato, Open Sans or System) and a heading font (the same, plus Playfair Display and Merriweather). A font shows when the learner's device has it; otherwise their system font stands in.
- Lesson title: how the title above each lesson looks: Plain, Banner (a band in the primary color) or Gradient (a band shading from primary to accent). The title's text turns white or dark, whichever reads better on the band. A lesson that opens with a heading matching its title shows that heading instead, with no title above it.
- Custom CSS: your own rules, added after the theme's. Use it for small changes such as
.block-callout { border-radius: 0; }. For safety it is cleaned before use:<and backslashes are dropped,url()may hold only an inlinedata:imagepicture (nothing loads from another site), and@import,expression(), script URLs and rules whose braces do not close are left out. The editor lists anything it left out as you type.
Click Save theme. The course preview and exported packages show the whole theme: colors, both fonts, the lesson title style and your custom CSS. The hosted course player uses the primary and background colors and the body font.
Contrast is yours to check
The theme editor does not stop you choosing text and background colors that are hard to read. Body text needs a contrast of at least 4.5:1 against its background (3:1 for large text) to meet WCAG 2.1 AA. On the slide canvas the accessibility audit flags text below that; see The accessibility checks.
Whatever theme the author's own screen uses, learner pages — the player, the preview, the public link and the review page — always use the light look.
Scenes courses
Courses on the slide canvas style the player around the slides instead: Tools → Player theme in the Scenes editor. It sets the accent (the Next button), the progress bar, the navigation bar and its text, the background around the slides, a logo (top left, top right or hidden), the navigation font (system sans-serif, serif or monospace, which every computer has, so nothing is downloaded), and whether slides have rounded corners and a drop shadow. The preview player and every exported package (SCORM 1.2, SCORM 2004, cmi5 and xAPI) show the same result; the package carries its own copy of the logo.
Anything you leave unchanged follows Settings → Branding: the brand color becomes the accent and the logo appears top left, with the brand name as its text alternative. A course's own choice always wins over the workspace's, field by field, and Use workspace branding clears the course's choices.
Navigation text needs 4.5:1 contrast against the navigation bar and the progress bar 3:1. If a color you pick falls short, the dialog says so and learners see it moved toward black or white just far enough to read. Button text is white or black, whichever reads on the accent. The Player theme has no custom CSS.
Your organization's branding
Settings → Branding sets how your organization appears in exported courses and review links, and is the starting point for every Scenes course's player theme. Only the organization's Owner can save it.
- Brand Name replaces "Scormbusters" in exported course headers.
- Logo: Upload Logo or Remove.
- Brand Color, as a hex color.
- Custom Footer HTML, added to the exported package's page after it is cleaned.
Click Save Branding.
Scormbusters' own branding
Exported packages carry no Scormbusters branding on any plan. Removing Scormbusters branding from the hosted learner experience, and the custom export footer, are part of Studio and Enterprise. A custom domain is Enterprise. See Plans and limits.
Part of the documentation: Build.
Found something here that does not match what the product does? That is a bug in the guide — see all guides or tell us from the Help Center.