See your email.
Before you
send it.

Yes. The interactive gallery contains actual captures of our own demonstration email, generated by Vision Preview on 5 October 2026. They are saved examples, not live renders or customer data. The workspace illustration at the top of this page is an illustrative mockup. Preview jobs capture your email inside the actual supported application: Apple Mail on Apple hardware, Android apps on Android emulators, and desktop and webmail clients in their respective environments. Where several Outlook labels share a capture, the results identify the underlying client and engine.

Yes. Share a public proof link so clients can view the captures, read Pre-Checks and leave comments. Guests enter a name, are labelled Guest, and can mention organisation members without seeing their email addresses. Mentioned members receive a branded email linking to the discussion. Anyone holding the link can see the shared comments and names, so do not use it for private team notes. Public guests cannot approve a version.

It records an organisation member’s approval of that exact version. Your team can approve even if some captures are pending or failed, based on the clients and requirements that matter to you. A newly generated version does not inherit the previous approval. This is a human sign-off—not an automatic send, a guarantee that every check passed, or a deliverability certification.

No. Its live browser view helps you edit HTML quickly, check responsive layouts and navigate from a visual block to its code. Save a private draft, then choose Generate previews to capture a new version in real email clients. Original proofs stay unchanged, and generating that new version uses your normal preview allowance.

It is a transparent 100-point checklist for supported HTML, link, asset, sender and content checks. Earned, deducted and unverified points are shown separately. Opening the private Pre-Checks tab runs eligible public link/image and sender checks, reusing recent results. Supported HTML findings can take you to their source. Sender authentication needs evidence from the actual sending platform; DNS records alone do not prove authentication. This is not an inbox-placement probability, SpamAssassin test or blocklist assessment. Public visitors see the available report without triggering external checks.

One click on Run AI QA Checks reviews all successful screenshots currently available for one email version and uses one check from your organisation’s monthly allowance. It never runs automatically. If a capture failed, the report tells you it was not analyzed. Running AI Visual QA again for that version uses another check. Its findings are advisory, stay separate from the 100-point Pre-Checks score and do not replace reviewing the original screenshots.

Yes. Each folder has a unique email address and saved email-client selection. Send a test to it from your platform and Vision Preview captures those clients. API submissions can use the same defaults or a subset. You can add clients to an individual proof without changing the folder, while its original source is available—retained for up to 30 days within the organisation’s source-storage allowance. Existing screenshots remain available when that source expires.

Timing depends on the client, the email’s length and images, the queue, and whether a rendering device needs to start. Screenshots appear as each client finishes, so you can begin reviewing available results while the others render. We don’t promise an identical completion time for every client.

Each selected client and appearance counts as one render: five selected clients use five renders, and light and dark count separately. Automatic retries, reopening screenshots and reselecting already-generated clients do not use extra renders. Adding a never-requested client or generating a new version uses the corresponding number of renders. API and email submissions share your organisation’s hourly and monthly allowances. Basic and Standard monthly usage resets on the Stripe subscription anniversary; Free resets on the first day of each month (UTC). Unused capacity does not roll over.

Create an organisation and invite your colleagues. Admins manage the organisation, members and billing. Users work with folders and previews. If you belong to multiple organisations, you can switch between them in the app.

Open a folder and copy its API example. Send your HTML and chosen email clients using the folder’s bearer token. You’ll receive a preview ID and polling command. Poll with the same token for image URLs as they become available, and check terminal failures. Keep your token private: it grants API access to that folder. Tokens do not expire automatically and can be rotated.