Most inbox placement tools answer a yes/no question: did the email land in the inbox, or in spam? For the last decade that was enough. Today it isn't. Gmail has Primary, Social, Promotions and Updates. Outlook splits Focused and Other. Yahoo blocks remote images by default. Mail.ru renders Cyrillic subjects with its own quirks. A one-word verdict hides all of it.
A screenshot-based test shows the actual rendered mailbox — the thing your recipient will see. Here is what that catches, why it matters, and how the free test at check.live-direct-marketing.online compares to paid alternatives that still do not offer screenshots.
A "delivered to inbox" verdict can still mean: landed in Promotions, rendered with a broken hero image, clipped after 102KB, had the subject truncated in the list view, showed "via sendgrid.net" next to the sender name, or was displayed as raw HTML on a ProtonMail client. Screenshots catch all of these. Verdicts catch none.
What verdict-only tests miss
Run the same email through a verdict-only tool and a screenshot tool, and you will find a surprising number of divergences. Here are the five we see most often.
Gmail tab placement
Gmail's tabbed inbox is not documented. There is no "Promotions" header a verdict tool can read. If the receiving mailbox happens to have tabs enabled (default for consumer accounts, off for Workspace in most cases), your marketing email almost always ends up in Promotions — technically inbox, practically invisible. A screenshot makes this obvious within two seconds.
Clipped and blocked images
Gmail clips any message larger than 102KB at the body level, showing a "View entire message" link. Yahoo and AOL block remote images by default unless the sender is in the address book. Outlook Web has its own image-blocking rules tied to SmartScreen reputation. A verdict tool says "inbox." A screenshot shows a broken mail with grey placeholder boxes.
Inline rendering bugs
Dark mode inverts your background but not your logo. Outlook 2019 strips padding from table cells. Gmail iOS crops fluid-width layouts at 600px. Mail.ru web re-flows HTML in unexpected ways. None of this shows up in an "authenticated, delivered to inbox" verdict.
RTL and Cyrillic edge cases
Arabic and Hebrew subjects in Gmail often show as mirror-text when the From field has a mixed-direction display name. Cyrillic subjects on Mail.ru and Yandex sometimes render with corrupt encoding when the mail server uses quoted-printable without a correct charset declaration. These are rendering issues only a screenshot surfaces.
Sender-name metadata
Gmail shows "via example.com" next to the sender name when the Return-Path domain does not match From. That tag kills trust signals in cold outreach. Verdicts do not flag it; screenshots do.
How screenshot tests work
The mechanics are simple, but the operations are not. For every supported provider, the testing service maintains a real mailbox. It hands you a seed address to BCC. When your mail arrives, a headless browser logs into that mailbox, waits for the message to render, then captures a screenshot and parses the headers.
- You request a test and receive 20+ unique seed addresses.
- You send your real email to those seeds (directly or as a BCC).
- The service logs into each mailbox via IMAP, Graph, or headless browser.
- It captures a screenshot, records placement folder, extracts headers.
- A dashboard surfaces every provider side-by-side, screenshots and all.
Gmail: Primary vs Promotions
The tab a Gmail user sees is a per-user machine-learning decision. The same email can land in Primary for one recipient and Promotions for another. Seed mailboxes approximate consumer behaviour — fresh accounts with tabs on and no prior interaction history. A screenshot showing Promotions is a strong signal that most consumer recipients will see the same.
Outlook: Focused and Other
Outlook.com and Microsoft 365 both split the inbox into Focused and Other. Other is not spam — it is "inbox, but deprioritised." Open rates on Other are about 40% of Focused. Outlook.com also has a separate Quarantine area visible only through admin tools, which catches tenant-level policy matches that never touch the user's mailbox. A screenshot of the user view plus a header line from the Quarantine report is the only way to see the full picture.
Yahoo: the image-blocking trap
Yahoo blocks remote images for any sender not already on the recipient's allow list. A hero-image-based newsletter design collapses into empty boxes. Even when your placement is Inbox, the rendered mail looks broken. A screenshot makes this immediate. Mitigation: lead with text, use alt text on every image, avoid image-only CTAs.
Mail.ru: Cyrillic subject rendering
Mail.ru and Yandex both expect UTF-8 encoded subjects with RFC 2047 encoding for anything non-ASCII. Some SMTP libraries default to ISO-8859-1 or send raw UTF-8 without encoding. The message arrives and looks fine in Gmail but shows as ????? ????? on Mail.ru. Screenshot tests catch these within seconds. Verdict tools do not.
Using screenshots in reporting
Screenshots close the loop with stakeholders who do not read header dumps. A marketing manager needs to see the rendered email, not a JSON blob saying spf=pass, dkim=pass. Export the screenshot grid to PDF, attach to a campaign post-mortem, and the conversation about "why did open rate drop" becomes a conversation about "because Outlook displayed a grey box for the hero image."
GlockApps is the best-known paid placement tool. It does not currently offer per-mailbox rendered screenshots. Its reports stop at folder verdicts and authentication metadata. If the rendered view matters to you — and for most modern email teams it does — screenshots are a non-trivial feature gap.