How to make a visual novel without coding
What replaces code in a no-code visual novel: a scene map, linked choices, an asset brief, and route testing, with a five-scene example to build first.

A visual novel engine asks you to write labels, jumps, menus, and image commands. A no-code tool asks for the same decisions in another form: scenes instead of labels, linked choices instead of menus, and generated or uploaded art instead of image commands. The syntax disappears; the design work does not.
This guide walks through what each piece of code is replaced by, using one small project you can build in an afternoon.
Example: a five-scene first project
Two roommates cannot find the key to a locked room on the night one of them is moving out. The map: opening in the flat → call the landlord → an ending where the move goes ahead; or opening in the flat → open the locked room → an ending where the real reason for the move comes out. That is five scenes in total: one shared opening, two branch scenes, and two ending scenes.
1. The scene map replaces labels and jumps
In a scripted engine, each scene is a label and each transition is a jump. Without code, each scene is a card and each transition is an arrow. Draw the five cards for the roommate story and the arrows between them before generating anything; if you cannot draw the arrows, the story is not ready to build.
In Pominis you can describe the premise to the agent and it drafts the map for you. Check that its scene board matches the five cards you drew, and change it where it does not, rather than accepting a bigger structure than you planned.
2. Linked choices replace menus
A menu in code is a list of options, each jumping to a label. In a no-code editor, a choice is a label the player reads and a scene it goes to. For the roommates, the opening ends with two: “Call the landlord” and “Force the lock”. Each one's destination is set on the scene itself, so a broken link is a visible problem on the board rather than a runtime error.
If a choice should depend on something earlier, such as whether the player found the spare key, that is the job of variables in an engine. In Pominis it belongs on the Interactive mechanics board, where the agent can set up flags and conditions for you. A five-scene first project rarely needs them.
3. An asset brief replaces image commands
Before generating many images, define a compact visual brief. Record the art style, lighting, recurring color palette, what each character looks like, and each location's defining features. This reduces visual drift and makes regeneration more deliberate.
- Character portraits: neutral reference plus only the expressions the story needs.
- Backgrounds: one establishing image per recurring location before variants.
- Key art: reserve special compositions for turning points and endings.
- Audio: use a small set of themes tied to location or emotion.

4. Dialogue still has to be written for the screen
Visual novel dialogue is read one text box at a time. Keep each beat focused, vary sentence length, and let expressions or backgrounds carry information that does not need to be repeated in narration. Choices should describe an intention or action, not hide their meaning behind vague wording.
When you ask AI for dialogue, ask for a change, not only “more dialogue”. For example: “Rewrite the opening so the player begins annoyed with the roommate and ends suspecting she is hiding why she is leaving.”
5. Testing replaces compiling
There is no build step to catch mistakes, so play instead. On the Pominis scene board, a scene that cannot be reached or points to a missing scene is flagged as Unlinked or Missing target; fix those first. Then use Play draft and click both choices in the roommate story from the opening to each ending.
- Complete every route at least once.
- Check that character names and appearance stay the same in every scene.
- Confirm neither ending depends on something the player never saw.
- Ask a new reader to play without explaining the controls or plot.
6. Publish the five scenes first
A short visual novel with a clean ending teaches you more than an unfinished long one. Publish the first complete version, ask readers where they stopped or replayed, and let that decide whether the next update needs more routes, stronger art, or clearer choices. Public, unlisted and private publishing are all free; HTML export needs a paid plan.

