Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 400,000 packages pre-installed, including spectacle with all npm packages installed. Try it out:

require("prop-types/package.json"); // prop-types is a peer dependency. require("react/package.json"); // react is a peer dependency. require("react-dom/package.json"); // react-dom is a peer dependency. var spectacle = require("spectacle")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

spectacle v2.2.2

ReactJS Powered Presentation Framework


Join the chat at Travis Status ReactJS based Presentation Library

Spectacle Boilerplate


Getting Started

The new best way to get started is by running create-react-app my-presentation --scripts-version spectacle-scripts. This will use create-react-app to create almost everything you need. This however, doesn't include publish scripts, and ejecting is required for fancy stuff.

The second best way to get started is by using the Spectacle Boilerplate.

Alternatively, you can npm install spectacle and write your own build configurations. We also provide full UMD builds (with a Spectacle global variable) of the library at dist/spectacle.js and dist/spectacle.min.js for more general use cases. You could, for example, include the library via a script tag with:

Note that we have webpack externals for react, react-dom, and prop-types, so you will need to provide them in your upstream build or something like linking in via script tags in your HTML page for all three libraries. This comports with our project dependencies which place these three libraries in peerDependencies.

But really, it is SO much easier to just use the boilerplate. Trust me.

One Page

To aid with speedy development / kicking the tires on spectacle, we support using a simple boilerplate HTML page with a bespoke script tag that contains your entire presentation. The rest of the setup will take care of transpiling your React/ESnext code, providing Spectacle, React, and ReactDOM libraries, and being raring to go with a minimum of effort.

We can start with this project's sample at one-page.html. It's essentially, the same presentation as the fully-built-from-source version, with a few notable exceptions:

  1. There are no imports or requires. Everything must come from the global namespace. This includes Spectacle, React, ReactDOM and all the Spectacle exports from ./src/index.js -- Deck, Slide, themes, etc.

  2. The presentation must include exactly one script tag with the type text/spectacle that is a function. Presently, that function is directly inserted inline into a wrapper code boilerplate as a React Component render function. The wrapper is transpiled. There should not be any extraneous content around it like outer variables or comments.

    Good examples:

    <script type="text/spectacle">
      () => (
        <Deck>{/* SLIDES */}</Deck>
    <script type="text/spectacle">
      () => {
        // Code-y code stuff in JS...
        return (
          <Deck>{/* SLIDES */}</Deck>

    Bad examples of what not to do:

    <script type="text/spectacle">
      // Outer comment (BAD)
      const outerVariable = "BAD";
      () => (
        <Deck>{/* SLIDES */}</Deck>

... with those guidelines in mind, here's the boilerplate that you can literally copy-and-paste into an HTML file and start a Spectacle presentation that works from the get go!

<!DOCTYPE html>
<html lang="en">
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width initial-scale=1 user-scalable=no" />
    <link href=",700" rel="stylesheet" type="text/css">
    <link href=",700" rel="stylesheet" type="text/css">
    <link href="" rel="stylesheet" type="text/css">
    <link href="" rel="stylesheet" type="text/css">
    <link href="" rel="stylesheet" type="text/css">
    <div id="root"></div>
    <script src=""></script>
    <script src=""></script>
    <script src=""></script>
    <script src=""></script>
    <script src=""></script>
    <script src=""></script>
    <script src=""></script>
    <script src=""></script>
    <script type="text/spectacle">
      () => {
        // Your JS Code goes here

        return (
          {/* Throw in some slides here! */}


After downloading the boilerplate, your first order of business is to open terminal and run npm install

Next run rm -R .git to remove the existing version control.

Then, to start up the local server, run npm start

Open a browser and hit http://localhost:3000, and we are ready to roll

Build & Deployment

Building the dist version of the slides is as easy as running npm run build:dist

If you want to deploy the slideshow to surge, run npm run deploy

⚠️ If you are deploying the dist version to GitHub Pages, note that the built bundle uses an absolute path to the /dist/ directory while GitHub Pages requires the relative ./dist/ to find any embedded assets and/or images. A very hacky way to fix this is to edit one place in the produced bundle, as shown in this GitHub issue.


Spectacle comes with a built in presenter mode. It shows you a slide lookahead, current time and your current slide:

Otherwise, it can also show you a stopwatch to count the elapsed time:

To present:

Note: Any windows/tabs in the same browser that are running Spectacle will sync to one another, even if you don't want to use presentation mode

Check it out:

You can toggle the presenter or overview mode by pressing respectively alt+p and alt+o.


Key CombinationFunction
Right ArrowNext Slide
Left ArrowPrevious Slide
SpaceNext Slide
Shift+SpacePrevious Slide
Alt/Option + OToggle Overview Mode
Alt/Option + PToggle Presenter Mode
Alt/Option + TToggle Timer in Presenter Mode
Alt/Option + AStart autoplay (if enabled)


Fullscreen can be toggled via browser options, or by hovering over the bottom right corner of your window until the fullscreen icon appears and clicking it.

PDF Export

Exporting a totally sweet looking PDF from your totally sweet looking Spectacle presentation is absurdly easy.

  • Run npm start
  • Open http://localhost:3000/
  • Add export& after the ? on the URL of page you are redirected to, e.g.: http://localhost:3000/#/?export&_k=wbyhif
  • Bring up the print dialog (ctrl or cmd + p)
  • Check "Background Graphics" to on if you are about that life
  • Change destination to "Save as PDF", as shown below:

If you want to print your slides, and want a printer friendly version, simply repeat the above process but instead print from http://localhost:3000/?export&print

Basic Concepts

Main file

Your presentation files & assets will live in the presentation folder.

The main .js file you write your deck in is /presentation/index.js

Check it out here in the boilerplate.

// index.js

import React, { Component } from 'react';
import {
  Appear, BlockQuote, Cite, CodePane, Code, Deck, Fill, Fit,
  Heading, Image, Layout, ListItem, List, Quote, Slide, Text
} from 'spectacle';

export default class extends Component {
  render() {
    return (

Here is where you can use the library's tags to compose your presentation. While you can use any JSX syntax here, building your presentation with the supplied tags allows for theming to work properly.

The bare minimum you need to start is aDeck element and a Slide element. Each Slide element represents a slide inside of your slideshow.


In Spectacle, themes are functions that return style objects for screen & print.

You can import the default theme from:

import createTheme from "spectacle/lib/themes/default";

Or create your own based upon the source.

index.js is what you would edit in order to create a custom theme of your own, using ReactJS style inline style objects.

You will want to edit index.html to include any web fonts or additional CSS that your theme requires.

createTheme(colors, fonts)

Spectacle's functional theme system allows you to pass in color and font variables that you can use on your elements. The fonts configuration object can take a string for a system font or an object that specifies it‘s a Google Font. If you use a Google Font you can provide a styles array for loading different weights and variations. Google Font tags will be automatically created. See the example below:

const theme = createTheme({
  primary: "red",
  secondary: "blue"
}, {
  primary: "Helvetica",
  secondary: { name: "Droid Serif", googleFont: true, styles: [ "400", "700i" ] }

The returned theme object can then be passed to the Deck tag via the theme prop, and will override the default styles.


In Spectacle, presentations are composed of a set of base tags. We can separate these into three categories: Main tags, Layout tags & Element tags.

Main Tags


The Deck tag is the root level tag for your presentation. It supports the following props:

controlsPropTypes.boolShow control arrows when not in fullscreen
contentHeightPropTypes.numbersBaseline content area height (default: 700)
contentWidthPropTypes.numbersBaseline content area width (default: 1000)
historyPropTypes.objectAccepts custom configuration for history
progressPropTypes.stringAccepts pacman, bar, number or none. To override the color, change the 'quarternary' color in the theme.
themePropTypes.objectAccepts a theme object for styling your presentation
transitionPropTypes.arrayAccepts slide, zoom, fade or spin, and can be combined. Sets global slide transitions. Note: If you use the 'scale' transition, fitted text won't work in Safari.
transitionDurationPropTypes.numberAccepts integer value in milliseconds for global transition duration.
autoplayPropTypes.boolAutomatically advance slides.
autoplayDurationPropTypes.numberAccepts integer value in milliseconds for global autoplay duration, defaults to 7000.

Slide (Base)

The slide tag represents each slide in the presentation. Giving a slide tag an id attribute will replace its number based navigation hash with the id provided. It supports the following props, in addition to any of the props outlined in the Base class props listing:

alignPropTypes.stringAccepts a space delimited value for positioning interior content. The first value can be flex-start (left), center (middle), or flex-end (right). The second value can be flex-start (top) , center (middle), or flex-end (bottom). You would provide this prop like align="center center", which is its default.
idPropTypes.stringUsed to create a string based hash.
maxHeightPropTypes.numberUsed to set max dimensions of the Slide.
maxWidthPropTypes.numberUsed to set max dimensions of the Slide.
notesPropTypes.stringText which will appear in the presenter mode. Can be HTML.
transitionPropTypes.arrayAccepts slide, zoom, fade or spin, and can be combined. Sets the slide transition. Note: If you use the 'scale' transition, fitted text won't work in Safari.
transitionDurationPropTypes.numberAccepts integer value in milliseconds for slide transition duration.


The notes tag allows to use any tree of react elements as the notes of a slide. It is used as a child node of a slide tag and its children override any value given as the notes attribute of its parent slide.

<Slide ...>
    <h4>Slide notes</h4>
      <li>First note</li>
      <li>Second note</li>
  {/* Slide content */}


The MarkdownSlides function lets you create a single or multiple slides using Markdown. It can be used as a tagged template literal or a function. Three dashes (---) are used as a delimiter between slides.

Tagged Template Literal Usage

<Deck ...>
## Slide One Title
Slide Content
## Slide Two Title
Slide Content

Function Usage

import slidesMarkdown from "raw!";

<Deck ...>

Layout Tags

Layout tags are used for layout using Flexbox within your slide. They are Layout, Fit & Fill.


The layout tag is used to wrap Fit and Fill tags to provide a row.


The fit tag only takes up as much space as its bounds provide.


The fill tag takes up all the space available to it. For example, if you have a Fill tag next to a Fit tag, the Fill tag will take up the rest of the space. Adjacent Fill tags split the difference and form an equidistant grid.

Markdown Tag


The Markdown tag is used to add inline markdown to your slide. You can provide markdown source via the source prop, or as children. You can also provide a custom mdast configuration via the mdastConfig prop.

Markdown generated tags aren't prop configurable, and instead render with your theme defaults.

sourcePropTypes.stringMarkdown source

Element Tags

The element tags are the bread and butter of your slide content. Most of these tags derive their props from the Base class, but the ones that have special options will have them listed:


This tag does not extend from Base. It's special. Wrapping elements in the appear tag makes them appear/disappear in order in response to navigation.

BlockQuote, Quote and Cite (Base)

These tags create a styled blockquote. Use them as follows:

  <Quote>Ken Wheeler is amazing</Quote>

CodePane (Base)

This tag displays a styled, highlighted code preview. I prefer putting my code samples in external .example files and requiring them using raw-loader as shown in the demo. Here are the props:

langPropTypes.stringPrism compatible language name. i.e: 'javascript'
sourcePropTypes.stringString of code to be shown

You can change your syntax highlighting theme by swapping the prism.js CSS file in index.html

Code (Base)

A simple tag for wrapping inline text that you want lightly styled in a monospace font.

Component Playground

This tag displays a two-pane view with a ES6 source code editor on the right and a preview pane on the left for showing off custom React components. React and render from ReactDOM are supplied as variables. To render a component use the domContainer mountNode. Any console output will be forwarded to the main console in the browser.

codePropTypes.stringThe code block you want to initially supply to the component playground. If none is supplied a demo component will be displayed.
previewBackgroundColorPropTypes.stringThe background color you want for the preview pane. Defaults to #fff.
themePropTypes.stringAccepts light or dark for the source editor's syntax highlighting. Defaults to light.
scopePropTypes.objectDefines any outside modules or components to expose to the playground. React, Component, and render are supplied for you.

Example code blocks:

const Button = ({ title }) => (<button type="button">{ title }</button>);
render(<Button title="My Button" />, mountNode);
class View extends React.Component {
  componentDidMount() {

  render() {
    return (<div>My View</div>);
render(<View />, mountNode);

Heading (Base)

Heading tags are special in that, when you specify a size prop, they generate the appropriate heading tag, and extend themselves with a style that is defined in the theme file for that heading. Line height can be adjusted via a numeric lineHeight prop.

fitPropTypes.booleanWhen set to true, fits text to the slide's width. Note: If you use the 'scale' transition, this won't work in Safari.
lineHeightPropTypes.numberSets the line height of your text.

Image (Base)

displayPropTypes.stringSet the display style property of the image
heightPropTypes.string or PropTypes.numberSupply a height to the image
srcPropTypes.stringImage src
widthPropTypes.string or PropTypes.numberSupply a width to the image

Link (Base)

The link tag is used to render <a> tags. It accepts an href prop:

hrefPropTypes.stringString of url for href attribute
targetPropTypes.stringSet the target attribute

List & ListItem (Base)

orderedPropTypes.boolRender as <ol>-tag
reversedPropTypes.boolSet the reversed attribute
startPropTypes.boolSet the start attribute, Default: 1
typePropTypes.boolSet the type attribute. Default: "1"

These tags create lists. Use them as follows:

Ordered lists:

<List ordered start={2} type="A">
  <ListItem>Item 1</ListItem>
  <ListItem>Item 2</ListItem>
  <ListItem>Item 3</ListItem>
  <ListItem>Item 4</ListItem>

Unordered lists:

  <ListItem>Item 1</ListItem>
  <ListItem>Item 2</ListItem>
  <ListItem>Item 3</ListItem>
  <ListItem>Item 4</ListItem>

S (Base)

The S tag is used to add inline styling to a piece of text, such as underline or strikethrough.

typePropTypes.stringAccepts strikethrough, underline, bold or italic

Table, TableRow, TableHeaderItem and TableItem (Base)

The Table tag is used to add table to your slide. It is used with TableHeader, TableBody, TableRow, TableHeaderItem and TableItem. Use them as follows:


Text (Base)

The Text tag is used to add text to your slide. Line height can be adjusted via a numeric lineHeight prop.

fitPropTypes.booleanWhen set to true, fits text to the slide's width. Note: If you use the 'scale' transition, this won't work in Safari.
lineHeightPropTypes.numberSets the line height of your text.

Base Props

Every component above that has (Base) after it has been extended from a common class that includes the following props:

italicPropTypes.booleanSet fontStyle to italic
boldPropTypes.booleanSet fontWeight to bold
capsPropTypes.booleanSet textTransform to uppercase
marginPropTypes.number or stringSet margin value
paddingPropTypes.number or stringSet padding value
textColorPropTypes.stringSet color value
textSizePropTypes.stringSet fontSize value
textAlignPropTypes.stringSet textAlign value
textFontPropTypes.stringSet textFont value
bgColorPropTypes.stringSet backgroundColor value
bgImagePropTypes.stringSet backgroundImage value
bgDarkenPropTypes.numberFloat value from 0.0 to 1.0 specifying how much to darken the bgImage image


The Typeface tag is used to apply a specific font to text content. It can either use a font that exists on the system or load a font from the Google Fonts library. Typeface requires either font or googleFont to be defined.

fontPropTypes.stringUse a font from the local system
googleFontPropTypes.stringUse a font from the Google Fonts library
weightPropTypes.numberNumeric weight value for the font. Default: 400.
italicPropTypes.booleanUse an italics variant of the font if it exists. Default: false.
<Typeface googleFont="Roboto Slab" weight={600}>
  <Text>This text is using bold Roboto Slab from Google Fonts.</Text>
<Typeface font="SF Text" weight={400} italic={true}>
  <Text>This text is using the San Francisco Text font from the system.</Text>

Third Party Extensions


RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free