Privacy first
Everything you write stays in your browser local storage. No server-side database is used, no user accounts are created, and no cookies are required for app data. You can review details in Privacy Policy and Terms (footer links).
Shape stories with visual narrative planning maps
Structurer helps writers build stories with visual planning maps, color-coded notes, characters, and narrative phases across built-in and custom structures.
Routes now use hash-based navigation (/#/...) so story and series slugs stay in the URL fragment,
not in server request paths.
Everything you write stays in your browser local storage. No server-side database is used, no user accounts are created, and no cookies are required for app data. You can review details in Privacy Policy and Terms (footer links).
Export any story as JSON and import it in another browser or computer. Your format is consistent across instances of Structurer.
You can also share a public JSON URL in read-only mode: on the dashboard open ⋯ Actions → Story → View shared story from URL, paste the source URL, then share the generated Structurer link. Recipients can save it as a dashboard Shared bookmark to reopen the latest version anytime.
You can also import community extension packs (custom structures) from the dashboard ⋯ Actions → Structure → Import/merge custom structures, then pick Import from a file or Paste custom structures JSON.
Need a story map for a work that is not in demos? Use Build AI import prompt to generate a strict JSON prompt in English while selecting the language you want for the analysis text in notes.
You can also paste a synopsis of your own story and ask the model to place those events on the structure, marking any missing phase with an absence note.
Demos use well-known films, but Structurer is designed for any narrative format: novels, short stories, screenplays, serialized fiction, and more.
No personal stories yet. to begin planning.
You can or load more from the extensions catalog.
Click a question to expand the answer.
A story structure is an organizational framework that helps shape a narrative arc: setup, rising tension, turning points, climax, and resolution. It does not replace creativity, but gives you a map to manage pacing and progression.
If you want background reading, start with Narrative structure (Wikipedia).
A story is your main planning workspace. Every story uses one narrative structure (for example Hero's Journey, Story Circle, or a custom structure) and renders each phase as a column.
You can think of a story as a visual planning canvas: you place notes inside phases and refine the story over time. To reorder phase columns by dragging, the story must use an altered structure (Story actions → Edit the structure creates a story-specific copy). A story also stores its own phase order, notes, and update history used for merge operations during import.
Series let you organize multiple stories into a sequence. This is useful for multi-arc projects, series planning, or alternate structure explorations of the same story.
Use Create series in the dashboard to name a series and pick stories with checkboxes. To add an existing story to a series later, open that story’s actions and choose Add story to series (available once you have at least one series), then pick the series from the list. Manage order, rename the series, and membership from Edit series in series actions on the dashboard.
Stories: double-click the story title in the dashboard list, on the story board header, or on a story title inside a series view. The title becomes an editable field: press Enter to save, Escape to cancel, or click outside to save.
Series: open Edit series from series actions (dashboard or series page) and change the Series name field at the top of the dialog.
Yes. Feel free to edit and experiment with demo stories (move notes, change phases, and tweak everything you want).
If you ever want to restore the demos, go to the dashboard and run Reset demos. Your personal stories and settings will be kept.
Hide demos can also read Hide demos and AI analyses when you have stories
imported from the Build AI import prompt flow (JSON with aiAnalysisImport: true).
That toggle hides built-in demos and those AI-tagged boards together.
Structurer currently includes these pre-built structures:
Phases are the structure steps (columns). Notes are cards inside those columns. Notes can represent plot points, themes, characters, or custom note types.
Drag notes with the handle (⋮⋮) to reorder them inside a phase or move them across phases. When the story uses an altered structure, a second handle beside the phase title lets you reorder columns. You can collapse notes for compact reading and open them in edit mode when needed.
In the story editor, click + in the phase header. Then select the note type from the menu. Character notes open from the character submenu so you can choose an archetype immediately.
New notes are saved locally and can be moved, collapsed, edited, and resized at any time.
Yes. Double-click the note header. The card collapses to a one-line preview so you can scan the story quickly; double-click again to expand.
Open the story board, then Actions → Note types & archetypes:
These custom definitions are saved in your browser and become reusable across stories.
Go to dashboard and open Add a structure not listed. For each phase, enter a name and optionally a short description (shown as help when editing a story), save, and the new structure will appear in the story creation selector.
For example, if you want to follow a structure like Freytag's Pyramid (which is not included by default), you can add its phases manually and save it as your own reusable structure.
You can also import ready-made custom structure packs from dashboard ⋯ Actions → Structure → Import/merge custom structures.
The interface and the built-in structures are available in English, Italian, and Spanish. Choose your language from Language in the footer. Your choice is saved in this browser. Unmodified demo stories switch to that language. A demo you have edited stays as you left it.
For other languages, or for regional narrative patterns, you can still import community extensions: custom structure packs that appear when you create a new story. See the next question: What are extensions and how do I use them?
Extensions are curated custom structure packs distributed as JSON files. They let you add new narrative frameworks (including non-English variants) without changing the built-in defaults.
To use one: download a JSON file from the extensions catalog, open dashboard ⋯ Actions → Structure → Import/merge custom structures, then choose Import from a file or Paste custom structures JSON.
See the catalog in EXTENSIONS.md and contribution rules in CONTRIBUTING_EXTENSIONS.md.
Demos are only examples. On the dashboard, open the last card under Stories (“Want analyses that aren’t in the demos?”) or use Build AI import prompt below: you get a ready-made prompt for an AI assistant (instructions stay in English; you can choose the language for the analysis text in the notes). Full steps for importing the JSON are on that page after you generate the prompt.
The same page can also turn a full synopsis of your own story into a board. The model must mark any phase the synopsis does not cover with an absence note, instead of inventing the missing beat.
AI output can contain mistakes; review notes after import. Use imports for personal study only and respect the work’s copyright.
Export a story from dashboard story actions. Import from ⋯ Actions → Story → Import/merge a story, then choose Import from a file or Paste story JSON in the dialog.
Recommended multi-device workflow: do one initial export/import to align IDs between the two copies. After that, repeat export/import for incremental merges.
If phase order differs between the two versions, merge is blocked and Structurer shows a side-by-side conflict modal so you can align the story manually and retry.
No. Structurer keeps your work in this browser’s storage only. The hosted app has no server-side copy of your boards and no per-user URLs that carry your data. If you send someone a link (even a story URL with a slug), they only open their local app — they will not see your story or structures.
To share a story, export it from Story actions (⋯ on the board) and send the JSON file or text. The recipient imports it from the dashboard ⋯ Actions → Story → Import/merge a story (Import from a file or Paste story JSON).
If your story JSON is hosted at a public URL, you can also share a read-only Structurer
link: open ⋯ Actions → Story → View shared story from URL, paste the JSON URL,
and share the generated /#/shared?src=... link. On that page, users can open the original
JSON and save it as a Shared bookmark in their dashboard to check updates later.
To share a structure template (phases only, not note content), open it from
Available structures on the dashboard, then use Export in the preview and
send that JSON. The recipient uses ⋯ Actions → Structure → Import/merge custom structures.
The file uses exportType: "structurer.structure" (legacy extension packs still use
structurer.custom-structures). Built-in templates keep their real id (e.g.
hero_journey). On import, any entry whose id is already a built-in framework in
the recipient’s app is skipped so you do not get a duplicate; if that id is not built-in
there, it is merged into custom structures like any other template.
Open a story, then click the magnifier icon on a phase header. Structurer opens a dedicated phase details page where you can keep writing comments without overcrowding the main board.
On desktop, notes for that phase are shown on the left (read-only for context) while comments are on the right. This keeps your story board clean while preserving all deeper notes.
You can add, edit, and delete as many comments as you need. Back in the story board, the phase shows a comment counter so you always know where extra context exists.
You can delete your stories and series one by one from the dashboard (use story/series actions).
If you want to do everything quickly, go to the dashboard and use Factory reset app data. Be absolutely sure before confirming: this permanently deletes all your local data from the browser storage (stories, series, custom structures/archetypes/note types, and app settings). There is no way to recover it.
If you only want to restore the demo stories, use Reset demos instead. And if you want to keep your current work, export stories first.
Pick a structure template, then choose a task: analyze a known work from its title, or turn a full synopsis into your story on that structure. Structurer builds one block of text (in English) to paste into ChatGPT, Claude, or another LLM—ask it to reply with only valid JSON in Structurer’s import shape. Choose the language for the note text separately so non-English writers get readable output without translating the instructions themselves.
"schemaVersion": 3, a canonical "structureId" (app
framework id), a human-readable "structure" name, and root
"aiAnalysisImport": true. Keep those fields so Structurer loads the correct columns and tags
the board as AI analysis (badge + Hide demos and AI analyses). If the
model omits aiAnalysisImport, the import is treated like a normal story.
When the task is Structure a synopsis, the prompt omits aiAnalysisImport so the board is your story, and it asks for absence notes wherever a phase is missing from the synopsis.
AI output can contain mistakes; review notes after import. Use imports for personal study only and respect the work’s copyright.
Simple, minimal, and personal.
Structurer is a personal app. It runs entirely in your browser for planning and note-taking.
All your data is saved locally in your browser storage. No server-side database is used, and no user accounts are created.
The app is served by a simple web server whose only role is to deliver the app files. There is no tracking, no cookies, and nothing is sent to any third party.
Minimal terms for a personal, local app.
Structurer is provided as a free, open source tool for personal narrative planning. There is no commercial or profit-making purpose behind the app.
Your data stays on your computer. Any stories, notes, series, custom structures, and settings you create or edit are stored only in your browser storage (localStorage). The app does not upload your data to any server.
Your actions are your responsibility. By using Structurer, you accept that all content you enter and any outcomes related to your use are yours alone.
No warranty. The app is provided “as is”, without any guarantees of performance, accuracy, or fitness for a particular purpose.
Forking and redistribution (GPLv3). If you fork or redistribute Structurer, you must republish any derivative work under the GNU GPLv3 (and include the corresponding source code).
This address is not a page in Structurer. If you typed it yourself, check for typos. Otherwise use the buttons below to continue.
Structurer keeps your stories, series, and notes only in this browser’s storage. URLs like
/your-story, /group/…, or
/slug/phase/1 point at data on your device—they are not
shareable web pages and do not load content from a server.
If someone sent you a link hoping you would see their board, ask them for a story export (JSON) and use ⋯ Actions → Story → Import/merge a story on your dashboard. For custom structure templates, they can share exported structure JSON and you can import it under ⋯ Actions → Structure.
The Help page has a short FAQ on sharing links versus files.
Tip: click a note to edit it, or press + in a column header to add a new note.
Hero's Journey
No notes in this phase yet.
Adjust the width for all columns.
Customize note colors (and custom labels). Built-in labels are fixed to avoid id/label mismatch.
Rename custom archetypes. Delete is available only when an archetype is not used by any character note.
Open a category to see commands.
Use the + button in each phase column to add your notes.
Only structures that are not used by any story can be removed. Select which unused structures to delete.
No unused structures to remove.
Valid structurer.structure JSON (preview export) or legacy structurer.custom-structures
(extension packs).
Paste a valid structurer.structure or structurer.custom-structures JSON payload.
Load a story JSON exported from Structurer.
Paste a story JSON payload (same shape as Export story, built-in demos, or older exports using
only the structure name). New exports use schemaVersion 3 and structureId.
Name the series and select which stories to include.
Open a category to see commands.
These changes apply only to this story's altered template. Rename the template under the story title (double-click).
Choose a series. The story will be added to the end of that series.
Drag by the handle to reorder. Remove a story with ✕ or add one below.
Please manually align the current story phase order, then repeat the import.
This will permanently delete everything stored in your browser. Stories, series, custom structures, custom archetypes, custom note types, note type display overrides, groups/series membership, and app settings will be lost and cannot be recovered.
This will replace demo stories and demo-only series with the default demo set.
This will delete all local data currently on this device and replace it with the backup data.
If you are not completely sure, export important stories first so you can re-import them later if needed.
Comments
No comments yet for this phase.