Which Novelez Export Should You Choose for Your Next Step?

You finish revising a visual novel in Novelez and open the Exports area. Four choices are waiting: script, images, HTML5, and Ren'Py. They all come from the same project, but they do not represent four quality levels of the same download. Each one hands a different part of the work to a different next step.

The useful question is not “Which export is best?” It is “What must someone do after receiving it?” A proofreader needs readable words. An artist needs files they can sort and replace. A tester needs the story to run. A developer preparing desktop releases needs an editable engine project. Choose from that job, and the file type usually becomes obvious.

Do you need someone to read the story or handle the art?

Choose the script export when the next person needs to inspect the writing without opening the editor. It turns the project's structured scenes into a plain text document. That makes it useful for a dialogue review, a translation estimate, an archive of the current wording, or a handoff to someone who should comment on the script rather than play the whole game.

It is not a playable build. A text file does not preserve timing, visual composition, transitions, music, or the feeling of reaching a choice after several minutes of reading. If the reviewer must judge whether a pause lands or whether a branch feels earned, give them something they can play instead.

Choose the image export when the next job is visual asset management. Novelez packages the AI-generated images attached to the project so you can review them as files, organize an art handoff, or keep a working copy outside the editor.

There is an important boundary. Images uploaded by the creator and stock assets are excluded from this package under the product's copyright-handling rule. The image download is therefore not a guaranteed backup of every visual visible in the game. Keep your original uploads and licensed stock files in your own source folder, with their licenses and purchase records. Use the exported image set for the generated material it actually contains.

These first two exports are parts, not performances. They are the right answer when somebody needs to work on one layer of the project and the wrong answer when somebody needs to experience the whole story.

When is HTML5 the practical handoff?

Choose HTML5 when the recipient should open the project as a game in a browser. Novelez produces a zipped web build containing the story and the assets needed for that build. After extracting it, the package can be opened through its entry page for testing or handed to someone who will place it on suitable web hosting.

This is usually the clearest handoff for a class review, an internal milestone, a portfolio copy, or a web developer who does not need to rewrite the game's logic. The recipient gets the running experience instead of a list of components. They can move through dialogue, see images in context, and follow choices.

Do not mistake a zip file for a published address. A public link still requires a host, correct file placement, and a test from the final URL. If the job is simply to let readers play the current Novelez version, the product's own web publishing path may involve less handling. The HTML5 package matters when you need possession of the web files or must deliver them outside that publishing flow.

Before handing it over, extract a fresh copy and run it from the same kind of environment the recipient will use. Check the opening, one choice, every media type in the first few minutes, and the ending. A successful download only proves that a package was created. It does not prove that the package was transferred intact or hosted correctly.

What does a Ren'Py export give you that HTML5 does not?

Choose Ren'Py when the next stage is engine work. Novelez creates a Ren'Py project with the scenario and available assets arranged for that tool. The recipient can unzip it, open the project with the Ren'Py SDK, inspect the generated script, adjust screens or configuration, and use Ren'Py's own build pipeline.

That makes it the useful route for desktop distribution, deeper interface changes, engine-specific features, or a handoff to a Ren'Py developer. It also changes who owns the next problem. Once the project enters Ren'Py, later modifications made there do not automatically flow back into the Novelez editor. Decide which side is the working source before two people start changing different copies.

A Ren'Py project is not the same thing as finished Windows, macOS, or Linux packages. Ren'Py's launcher creates platform distributions after you configure and test the project. You still need to inspect the generated script, confirm media and fonts, set build information, run script checks, and test the actual distributions on their target systems. Export moves the work into a production environment; it does not silently complete release engineering.

HTML5 and Ren'Py can both lead to something playable, but they answer different handoff questions. HTML5 says, “Open this web experience.” Ren'Py says, “Continue building this project in the engine.” If nobody on the next step intends to edit engine files or create platform packages, the extra flexibility of Ren'Py may only create extra work.

Why can an exported game disappear from the completed list?

Novelez treats a game build export as a completion marker. The Exports area keeps the latest valid exported version available for another download. If the project is edited afterward, that older version no longer represents the current project and leaves the completed list. Export again when the revision is ready, and the newer state becomes the current handoff.

This behavior is a useful reminder, not version control. Do not rely on the list as a permanent archive of every milestone. Give meaningful names to packages you keep, store them in dated release folders, and include a short note about what was tested. If an external collaborator is already using one build, tell them when a newer package replaces it.

The same rule clarifies when not to export. A project that is still changing every hour does not need a trail of nearly identical game packages. Use browser preview while editing. Export when a version has a recipient, a purpose, and a small verification checklist.

A decision you can make in one minute

Start with the next action:

• Someone will edit, translate, or comment on the words: export the script.
• Someone will sort or replace generated visuals: export the images, while keeping original uploads and licensed stock files separately.
• Someone will play or host a self-contained web package: export HTML5.
• Someone will continue development in Ren'Py or prepare platform distributions: export the Ren'Py project.

If two jobs are happening, send two deliberate outputs instead of the largest package by habit. A translator may need the script and a playable HTML5 build. An artist may need the generated image set and a short scene list. A Ren'Py developer may need the project plus your separate source archive for excluded assets and licenses.

The best export is the smallest complete handoff for the next person. Before your next Novelez milestone, who must receive the work, and do they need to read it, sort it, play it, or continue building it?