Imports, Exports, and Drafts

Template Studio supports file-based handoff and browser-based draft recovery. Those workflows are useful, but they also introduce replacement and conflict decisions you should understand before relying on them.

Import JSON

Use the more-actions menu beside Publish and choose Import JSON... when you want to load a builder document from a file.

Import is designed for Template Studio document JSON, not arbitrary HTML. When the imported file is accepted, the editor loads that document into the current builder session.

Replace-import confirmation

If the current document has unpublished changes relative to the last published version, Template Studio can ask you to confirm before replacing it with an imported file.

That extra prompt exists to prevent accidental loss of in-progress work. Treat it as a safety checkpoint, not an annoyance.

Export formats

The more-actions menu supports export as:

• HTML
• JSON
• MJML

Use JSON when you need the builder document itself. Use HTML or MJML when you need compiled output for review, portability, or downstream use outside the builder.

Persist drafts locally

Template Studio can keep a local browser draft when Persist Template is enabled in the editor settings.

This helps when:

• you accidentally close the editor
• you want recovery protection while drafting
• your session is interrupted before you publish

Because those drafts live in the browser, they are best treated as a convenience and recovery mechanism, not as the final system of record.

Local versus incoming conflict handling

When Template Studio opens, it can detect a mismatch between the incoming saved version and a locally persisted draft.

If that happens, the editor can ask whether you want to continue with the local version or the incoming saved version. Choose carefully:

• use the local version when your unpublished browser draft is the work you want to keep
• use the incoming version when the saved dashboard record is the correct source of truth

Best practices

• Publish important milestones instead of relying only on local drafts.
• Use JSON export before major experiments that may be hard to reverse.
• Read replacement prompts closely before confirming an import.
• Clear local uncertainty by publishing once a teammate-approved version is ready.

Troubleshooting