# What is demo mode?

Demo mode allows potential readers to discover a portion of your story before committing to a full read. It's an excellent marketing tool to attract new readers by giving them a taste of your universe and narrative style.

A strategic sample

Demo mode is comparable to a free chapter of a book. It should be long enough to captivate the reader, but stop at a strategic moment to make them want to continue.

# Enabling demo mode on your story

The first step is to enable demo mode in your story's general settings. Without this activation, any breakpoints configured on steps will have no effect.

1

Open story settings

Go to your story's dashboard, then click the "Settings" tab to access the general settings.

2

Enable the "Demo mode" toggle

In the dedicated section, enable the "Demo mode" toggle. A text field will appear to customize the message displayed at the end of the demo.

3

Customize the end message

Write an engaging message that will encourage the reader to create an account to continue reading. This message will be displayed when they reach a breakpoint.

Prerequisite

If the "Demo mode" toggle is not enabled in the story settings, any breakpoints configured on steps will be ignored and demo mode will not work.

# Setting demo breakpoints

Once demo mode is enabled, you need to mark certain steps as demo breakpoints by enabling the Demo breakpoint toggle in the step editor. When a reader in demo mode reaches one of these steps, reading stops and a message invites them to create an account or sign in to continue.

1

Identify strategic steps

Choose the steps where the demo should stop. Ideally, place them after a moment of intrigue or a cliffhanger.

2

Enable the "Demo breakpoint" toggle

In the step editor, enable the "Demo breakpoint" option to mark the step as the end of the demo.

3

Verify coverage

Make sure all possible paths in the demo portion lead to at least one breakpoint, to prevent the reader from getting stuck.

Demo breakpoint configuration
The "Demo breakpoint" option in the step settings.

# How demo mode works

When a non-logged-in reader accesses a story with demo mode, they can start reading immediately without needing to create an account. Reading proceeds normally until the reader reaches a demo breakpoint. At that point, a screen invites them to create a free account to access the full story.

  • No account needed — Readers can start reading without any sign-up.
  • Normal reading — During the demo, the reading experience is identical to the full version (choices, variables, events).
  • Gradual stop — The demo naturally stops at the breakpoint, with an invitation message to continue.
  • Seamless resume — Once registered, the reader picks up where they left off without losing their progress.
Demo end screen
The screen shown to the reader when they reach a demo breakpoint.

# Gift codes (Story Gifts)

Gift codes (story gifts) allow you to generate unique codes that grant access to your full story for specific users. It's an ideal tool for offering your story to beta testers, partners, or as part of promotions.

  • Unique codes — Each code is uniquely generated and can only be used once.
  • Targeted assignment — You can assign a code to a specific user or leave it open to anyone who has it.
  • Usage tracking — View which codes have been used and by whom.
  • Expiration management — Set an expiration date for codes if needed.
Gift code management
The gift code management interface lets you create, track, and manage granted access.

# Best practices for breakpoint placement

  • Create a cliffhanger — Stop the demo at a moment of narrative tension to make the reader want to know what happens next.
  • Show diversity — The demo portion should include at least one branching point to illustrate the interactive nature of your story.
  • Introduce key characters — Make sure the main characters appear in the demo.
  • Avoid demos that are too short — A 2-3 step demo isn't enough to captivate. Aim for at least 5 to 8 steps to provide a real experience.
  • Cover all paths — Verify that every possible path in the demo leads to a breakpoint. No path should lead to a dead end or go beyond the demo zone.
Important verification

Before publishing, test your demo by taking every possible path from the starting step. Make sure all paths lead to a breakpoint and that the experience remains coherent and satisfying, even in the truncated version.