How to Protect a Browser-Based AI Dialogue Project

You should be able to draft and generate a dialogue without creating an account. RealDubbing therefore keeps guest Dialogue projects—including generated line audio—in the browser's local storage.

That is convenient and private, but local storage is not the same as permanent project hosting. A reliable workflow combines automatic browser saving with occasional downloadable backups.

What is saved in the browser

The Dialogue workspace saves the project title, line order, character names, text, voice settings, performance controls, and generated audio for each line. It does not need to send the project to an account just to preserve your work.

The data belongs to the current browser profile on the current device. Opening the site in another browser, a private window, or another computer creates a different local workspace.

Understand the storage limit

Browsers place a quota on local storage, and generated audio is much larger than text. The exact capacity varies by browser and device. A short project may fit comfortably while a long scene with many regenerated takes can approach the limit.

RealDubbing always tries to save the complete project first. It avoids storing a second duplicate of the combined WAV. If the quota is full, it preserves the script and settings, then removes the oldest generated clips from the saved copy only until the project fits. The open editor is not changed, and a warning tells you to download a backup.

If local storage is unavailable—sometimes the case in strict private modes—the editor still works while the tab is open, but you should export a backup before leaving.

Download a project backup

Use Download backup in the Dialogue project bar. The JSON file contains the editable project and the generated per-line audio that is still available. Store it alongside the final WAV and source script.

Back up at sensible milestones:

• after casting the characters;
• after approving a difficult scene;
• before clearing browser data or changing devices;
• before a major rewrite;
• when the browser shows a storage warning.

The backup is a normal local file. It does not create an account or upload the project.

Restore JSON or start from SRT

Use Import JSON / SRT to restore a RealDubbing backup. The editor validates the main fields and reconstructs the project without trusting executable content from the file.

You can also import subtitle files. Each SRT cue becomes one Dialogue line. If a cue begins with Speaker:, that name is used as the character; otherwise the workspace assigns a default character name that you can edit.

After an SRT import, review line breaks before generating. Subtitle cues are often divided for reading speed rather than natural speech rhythm.

Export audio separately from the project

The WAV export is the finished audio asset. The JSON backup is the editable project. Keep both:

• WAV: place it in a video editor, audio editor, presentation, or publishing workflow.
• JSON: reopen the characters, text, voices, and individual clips in RealDubbing.
• Original script or SRT: retain the source of truth for editorial changes.

One file cannot replace the others. A WAV cannot recover editable lines, and a project backup is not as convenient for publishing.

A safe guest workflow

For short experiments, automatic local saving may be enough. For any work you would be unhappy to recreate, download a backup at the end of each session. This keeps the no-login experience fast while giving you direct control over where the project lives.