Review and Save
This page explains how End Users review and save email content in the Editor plugin.
Review tools help users check rendering before leaving the editor. Save behavior helps integrators understand how saved content returns to their product.
Preview Options
The editor supports multiple preview modes:
| Preview mode | What it shows | Best for |
|---|---|---|
| Desktop preview | Shows the email in a desktop-width preview. | Checking the default desktop layout and visual hierarchy. |
| Mobile preview | Shows the email inside a mobile device preview. | Checking responsive layout, image scaling, and mobile readability. |
| Inbox Preview | Shows how the email may render in selected email clients. | Testing rendering differences across inboxes and dark mode. |
Users can open preview from the editor top bar.
Desktop preview shows the email in a desktop layout.
Use it to review:
- Overall email width and alignment.
- Hero sections and large images.
- Text hierarchy.
- Button placement.
- Desktop spacing and section order.
Desktop preview is useful before final review, especially for emails designed around wider layouts.
Mobile preview shows the email in a mobile device frame.
Use it to check:
- Whether content stacks correctly on mobile.
- Whether text remains readable.
- Whether buttons are easy to tap.
- Whether images resize as expected.
- Whether long sections still make sense on a narrow screen.
The preview may also provide a QR code so users can scan and review the email on a phone.
Inbox Preview lets users check how an email may render in different email clients, devices, browsers, and modes.
Email HTML can behave differently across clients. A design that looks correct in one inbox may have spacing, image, font, dark mode, or layout issues in another. Inbox Preview helps users find those issues before using the email in a campaign.
Available clients
Inbox Preview supports client groups such as:
| Group | Examples |
|---|---|
| Desktop | Apple Mail, Outlook for Mac, Outlook 2013, Outlook 2016, Outlook 2019, Outlook 2021, Office 365, IBM Notes, Lotus Notes, Thunderbird. |
| Mobile and tablet | iPhone, iPad, Gmail App, Outlook App, Android Gmail, Android Outlook, Samsung Mail. |
| Web-based | Gmail, Outlook, Office 365, Yahoo Mail, AOL Mail, Comcast, Mail.ru, Web.de, G Suite, T-Online.de. |
| Dark mode | Selected desktop, mobile, and web clients that support dark mode previews. |
| Accessibility and fallback views | Color blindness view and plain text view, if available in your plan. |
The available client list may change as email clients, operating systems, and supported rendering environments are updated.
How users run Inbox Preview
Users can:
- Open Preview from the editor top bar.
- Choose Inbox Preview.
- Select the email clients or client groups they want to test.
- Click Run Preview.
- Open the generated previews and review rendering issues.
Users can select only the inboxes they care about, such as popular clients, recently selected clients, dark mode clients, or known troublemakers.
Each selected client may count as one preview usage. For example, testing five selected clients may consume five preview credits.
What users should check
When reviewing Inbox Preview results, users should look for:
- Broken or missing images.
- Unexpected spacing or alignment.
- Button rendering issues.
- Text color problems in dark mode.
- Background image fallback behavior.
- Font differences.
- Mobile stacking issues.
- Outlook-specific rendering differences.
Inbox Preview availability and usage may depend on your plan and available credits.
Save
The editor provides save tools to protect the user's work and send the latest email content back to your product.
There are two main save behaviors:
- Auto Save: saves changes while the user is editing.
- Manual Save: lets the user explicitly save from the editor top bar.
Both save behaviors can create version history. For integrated products, the Push URL callback is still the source of saved content received by your backend.
The editor supports auto save.
Auto save helps preserve the user's latest work while they edit. The top bar may show the latest saved time so users can understand whether recent changes have been saved.
Auto save improves the editing experience, but integrators should still treat the Push URL callback as the source of saved content received by their backend.
Users can also click Save in the editor top bar.
When the user saves:
- The Editor plugin saves the latest email state.
- The Editor plugin sends saved content to your configured Push URL.
- Your backend stores the returned HTML and editor data.
- Your product can continue its workflow, such as showing a preview, draft status, or campaign setup page.
Do not rely on iframe state, browser state, or the Return URL to retrieve final saved content.
Version History
The editor supports version history for saved email content.
Both auto save and manual save can create historical versions. When auto save is enabled, the editor can save versions at regular intervals, such as every 15 minutes. Users can open version history from the latest saved status in the top bar.
In version history, users can:
- View previous saved versions by time.
- Select a version from the history list.
- Preview the selected version before restoring it.
- Restore the selected version when they want to roll back recent changes.
Restoring a version replaces the current editor content with that historical version. After restoring, users should continue editing or click Save when they are ready to send the restored content back to your product.
For integrators, version history is an editor-side recovery tool. Your backend should still treat the Push URL callback as the source of saved content received from the editor.
Export HTML
The editor supports exporting the email as HTML.
Use HTML export when users need a standalone email HTML file for review, migration, or use in another tool.
Exported HTML is separate from the integration save flow. For integrated products, saved content should still be handled through the Push URL callback so your backend has the latest version.
What Integrators Should Know
Preview, save, and export features are part of the user experience inside the editor.
Your integration should:
- Let users open preview before saving.
- Explain which preview modes are available in your plan.
- Treat the Push URL callback as the source of saved email content.
- Store saved HTML and editor data on your backend.
- Decide whether exported HTML is available to your End Users.
Training Notes
When training End Users, explain the workflow like this:
- Use Desktop preview to review the main layout.
- Use Mobile preview to check mobile readability.
- Use Inbox Preview when you need client-specific rendering checks.
- Rely on auto save while editing, but click Save before leaving the workflow.
- Use Export HTML when you need a standalone HTML copy.
Updated about 1 month ago