Help & Support

Pinned Comments

Click anywhere on the email preview to leave a comment at that exact location. A numbered pin will appear for easy reference.

General Comments

Use the comment input at the top of the sidebar for feedback that doesn't relate to a specific part of the email.

Resolving Comments

Click "Resolve" to mark a comment as addressed. Resolved comments are hidden by default but can be shown using the filter.

Guest Comments

Reviewers don't need an account. They can enter their name when leaving feedback.

Uploading New Versions

Click "New Version" to upload an updated email. Previous versions are preserved for comparison.

Version History

Access previous versions from the version dropdown. Each version maintains its own comments.

Locking Versions

Lock a version to prevent new comments when you've finalized a design.

Render History & Retention

Your email HTML is kept indefinitely — you can always view and preview any version. Email client render screenshots are retained based on your plan: 7 days for Free, 90 days for Pro, and 1 year for Business. You can re-render any older version at any time.

Creating a Team

Go to Teams from your dashboard. Click "Create Team" and invite members by email.

Team Projects

Assign projects to a team so all members can view and manage them.

Sharing with Others

Use share links for clients or stakeholders outside your team. They can comment without creating an account.

What is the approval workflow?

Lets team members formally sign off on a version before sending. Each version shows a status badge — "Pending" or "Approved".

Enabling it

Open your project, click "Settings" in the toolbar, and toggle on "Approval Workflow". Requires an active Pro subscription.

Approving a version

Click the "Approve" button in the preview toolbar. It turns green once confirmed. Click again to revoke.

New versions

Approval is per-version. New versions start unapproved; previous approvals are preserved with attribution in version history.

Who can approve

The project owner and any team members. Guests can see status but cannot approve.

Notifications

Approvals trigger notifications to connected Slack channels and configured webhooks.

What is email rendering?

Shows exactly how your email looks across different clients and devices — Gmail Android, Outlook Windows, Apple Mail iOS, and more. Different clients interpret HTML differently.

Supported clients

Outlook (classic and new on Windows, Mac, Web, iOS and Android), Gmail (Web on Mac and Windows, Android and iOS), Apple Mail (Mac and iOS). More clients added based on user feedback.

How it works

Click the "Render" button in the preview toolbar, select clients, then "Render Previews". Your email is sent to real clients on real devices and screenshots captured.

Interpreting results

Look for layout issues, broken images, font differences, and spacing problems. Pay special attention to Outlook, which has the most rendering quirks due to its Word-based HTML engine.

Merge tags & ESP code ("Clean it up")

Templates from ESPs (Salesforce AMPscript, Klaviyo, Mailchimp, Liquid, and similar) contain merge tags and logic that only resolve when the email is sent, so before that they show as raw code in the preview. When we detect this, a banner appears with a "Clean it up" toggle that strips the template logic and swaps merge fields (like %%FirstName%% or {{ first_name }}) for readable [First Name] placeholders. Leave it on when you render and the real-client screenshots use the cleaned version too. It's display-only — your stored HTML, downloads, and the editor always keep the original bytes.

Free plan

Free users can preview HTML and use "Send Test" to check rendering on their own devices. Automated multi-client rendering requires Pro.

Setup

Connecting Your Account

Importing Emails

Getting Started

Connecting Your Account

Importing Designs

What the API does

Upload email HTML, trigger renders on real devices, and fetch light and dark mode screenshots from code. Your pipeline renders, your team reviews in the normal preview UI. Included with the Business plan.

Getting started

Create an API key in Settings → API Keys, then follow the API documentation. It includes a quick start, an OpenAPI spec, and a TypeScript SDK (npm install emailqa).

Testing without using your quota

Sandbox mode ("test": true) returns instant fake results so you can build and test your integration without consuming render previews or fleet time.

Webhooks

Subscribe to render.completed and other events to get notified the moment renders finish. No polling required.

The status page

status.emailqa.live shows the live health of the website, the app and API, and the real device render pipeline. An independent monitor outside our own servers checks all three every minute, so the page stays up even if EmailQA itself goes down.

Something seems slow or broken?

Check the status page first. If it shows an incident, we already know about it and are working on it. If everything is green and you still have a problem, email [email protected] and a real person will get back to you.

Uptime history

The page keeps 90 days of daily uptime for each part of the service, along with notes on past incidents. Monitoring launched in August 2026, so history builds from there.

Private Mode

Enable Private Mode in Project Settings to restrict access to only you and your team.

Share Links

Share links use unique, unguessable URLs. Regenerate the link anytime to revoke access.

Credentials

Integration credentials are never stored in plain text — OAuth tokens are held server-side; API keys are encrypted at rest.