The visual novel development checklist

Use this list before you publish each chapter — whether you ship on Ren'Py, Unity, or Arleco. Copy it into your notes and check items off; missing one obvious broken route hurts reviews more than missing a background variant.

Story & structure

  • Chapter has a clear opening hook in the first few beats
  • At least one meaningful choice (or deliberate kinetic stretch with purpose)
  • Cliffhanger or resolution that justifies the next episode
  • Character voice stays distinct in dialogue (read aloud test)
  • No placeholder “Lorem” or TBD lines left in publish path

Branching & logic

  • Every choice leads somewhere — no dead-end nodes
  • All endings in this chapter are reachable from at least one path
  • Metric / stat changes documented if gates exist later
  • Key items granted once; no duplicate grants on replay within same save
  • Prior-chapter choices respected if this episode branches on them

See how to write branching stories for design patterns that keep forks coherent.

Art & presentation

  • Backgrounds assigned for every scene (or intentional blank called out)
  • Character sprites show correct expression for tone
  • Text readable on mobile — font size and contrast checked
  • CGs (if any) match aspect ratio and file size limits
  • Content flags accurate (mature language, horror, etc.)

Audio (if used)

  • Music loops cleanly or fades appropriately
  • SFX not clipping or startling on default volume
  • Rights cleared for any non-original tracks

Technical & saves

  • Playthrough from chapter start on a fresh save file
  • Continue from checkpoint after refresh / re-open
  • Restart chapter clears progress for this episode only (if offered)
  • Validation passes in your tool (orphans, missing entry, broken links)
  • Preview on phone width, not just desktop

Publish & discover

  • Episode title, short description, and thumbnail set
  • Publish date or schedule confirmed (timezone aware)
  • Series page lists chapter in correct order
  • Previous chapter marked complete path for sequential unlock (if used)
  • Short announcement ready (blog, Discord, social) — see publishing online

After launch (first 48 hours)

  • Play once on live URL, not just studio preview
  • Watch for reader confusion in comments or Discord
  • Log typos for a quick patch; avoid rewriting plot mid-week unless critical
  • Note metrics: completion rate, drop-off beat, return readers next chapter

Scope sanity

If this checklist takes longer than fixing the chapter, the chapter may be too big. Split oversized episodes — weekly serial fiction wins on consistency, not word count.

New to the full pipeline? Start with how to make a visual novel and pick your stack in our engine comparison.

Run validation in the studio

Open creator studio