---
title: "What Email Preflight Checks (and What It Deliberately Does Not)"
description: "Preflight is automated quality on compiled email output - variables, links, images, accessibility, and structure. It is not deliverability, inbox placement, or campaign analytics."
canonical: "https://memo.ly/blog/what-email-preflight-checks-and-what-it-does-not"
updated: "2026-07-31"
---

# What Email Preflight Checks (and What It Deliberately Does Not)

Preflight is automated quality on compiled email output - variables, links, images, accessibility, and structure. It is not deliverability, inbox placement, or campaign analytics.

*Guide · 9 min read · Updated 2026-07-31*

Teams use “preflight” to mean everything from a mental checklist to a Litmus inbox preview. In Memo, preflight means something narrower and more useful: deterministic checks on the email you actually export - run on the same compiler output that powers preview, export, and test send.

## What preflight is

Preflight reads compiled HTML and plain text, walks the document structure, and returns findings you can fix in the editor. Categories include content and variables, links, images and assets, HTML hygiene, rendering, accessibility, brand compliance, and compliance-adjacent footer checks - each with a severity and a plain recommendation.

## What preflight is not

- Not a substitute for your ESP - Memo does not send campaigns or hold audiences.
- Not deliverability scoring or inbox placement guarantees.
- Not open/click analytics - those live in your sending platform.
- Not a legal review - footer checks are mechanical, not counsel.

## When to run it

Run preflight after meaningful edits and before review or export. Pair it with human judgment on message and brand. Pair it with a controlled [test send](https://memo.ly/docs/send-a-controlled-internal-test.md) when you need a real inbox render - preflight first, eyeballs second.

## How Memo uses preflight in the workflow

Findings surface in the editor. Teams can gate approval or export until critical issues clear. That keeps reviewers off broken-link duty. See [Resolve preflight findings](https://memo.ly/docs/resolve-preflight-findings.md) for the fix loop.

## FAQ

### Does preflight guarantee my email will reach the inbox?

No. Preflight catches fixable quality issues in the email file. Inbox placement depends on sender reputation, list hygiene, and signals outside the design studio.

### Is preflight the same as inbox preview tools?

No. Preview tools show client rendering. Preflight checks structural quality, links, variables, and policy-oriented footer elements on compiled output.

### Can I turn preflight rules off?

Core safety rules stay on. Quality profiles let teams tune severity for marketing vs transactional intent where the product supports it.

### Does Memo run preflight on every save?

Runs are tied to meaningful compile events and workflow gates - not a vague “score” that changes silently on every keystroke.

## Related
- [The email preflight checklist](https://memo.ly/email-preflight-checklist.md)
- [What to check before you send](https://memo.ly/blog/what-to-check-before-you-send.md)

[View HTML version](https://memo.ly/blog/what-email-preflight-checks-and-what-it-does-not) · [Blog](https://memo.ly/blog)