HTML Export
Nongine can export your entire visual novel as a standalone HTML file that runs independently in any modern browser. This export option is ideal for distributing your project as a downloadable file, hosting it on your own server, or archiving a self-contained copy that does not depend on Nongine's hosting infrastructure.
How to Export
To export your project, open the project settings menu and select "Export as HTML." The editor will compile your project into a single HTML file that bundles all of your assets, scripts, and the player runtime together. Depending on the size of your project and its assets, this process may take a few seconds to a couple of minutes. When the export is complete, your browser will download the HTML file automatically. The file name defaults to your project title with a .html extension.
How It Works
The exported HTML file contains everything needed to run your visual novel. The player runtime is embedded as inline JavaScript. All images are encoded as base64 data URIs or packed into the file as binary blobs. Audio files are similarly embedded. The project's node graph, variable definitions, theme configuration, and all sequence content are serialized as a JSON data structure within the file. When the reader opens the HTML file in their browser, the embedded player reads this data and runs the visual novel exactly as it would on the hosted version.
Because everything is contained in a single file, the export requires no server, no internet connection, and no additional files or folders. The reader simply double-clicks the HTML file or opens it in their browser. This makes distribution extremely simple: you can email the file, upload it to a file sharing service, attach it to a forum post, or include it on a USB drive.
Offline Support
The standalone HTML export works fully offline. Once the reader has the file on their device, they can open and play it without any network connection. Save data is stored in the browser's local storage, keyed to the file path, so progress is preserved between sessions as long as the file remains in the same location. If the reader moves or renames the file, their save data may not carry over, but the project itself will still run correctly.
Considerations and Limitations
The primary trade-off of the standalone export is file size. Because all assets are embedded in the HTML file, projects with many high-resolution images or long audio tracks can produce very large files. A project with modest assets might export to a 5-10 MB file, while an asset-heavy project could reach 100 MB or more. To keep export size manageable, consider compressing your images to WebP format and using OGG or MP3 for audio at reasonable bitrates.
The standalone export represents a snapshot of your project at the time of export. It does not update when you make changes in the editor. If you want to distribute an updated version, you must export again and redistribute the new file. Unlike the web publish option, there is no automatic versioning or rollback for exported files.