Email rendering testing
We test how an email displays across different mail clients and devices (Gmail, Outlook, Apple Mail, mobile, dark mode): we find coding issues, breaking blocks, distortions. Honestly and bluntly upfront: testing reduces risks and shows the real picture, but does NOT make display identical everywhere — this is a limitation of email as a medium. And rendering testing ≠ sales. We find and help fix issues, without promises of pixel-perfect and sales growth.
Email rendering testing — overview
Email rendering testing is checking how an email displays across a matrix of mail clients and devices: running the email through preview services (many clients/versions), checking desktop/mobile, dark mode, display without loading images, identifying broken blocks and distortions, a report with issues and fix recommendations. The work: client matrix, run, analysis, report. Honestly about 'a test ≠ identity everywhere', this is key and fundamental: mail clients render HTML differently (especially Outlook on the Word engine), dark mode is unpredictable — testing shows where and what breaks and helps bring it to 'good enough everywhere', but achieving identical pixel-perfect display across all clients is impossible; this is a limitation of the medium. 'We test — it will be the same everywhere' = a lie. Honestly about 'a test finds but does not fix by itself': testing reveals issues; fixing the coding is separate work (we can do it, see 553/558). Honestly about 'a snapshot at the time of the test': clients and their versions update, new ones appear — the test is relevant at the time of running, not forever. Honestly about 'a test ≠ sales': correct rendering improves perception and reduces the risk of a 'broken' email, but by itself does not increase sales — they depend on the offer/content/base. Honestly about 'matrix coverage': we test a reasonable set of popular clients; rare/corporate builds may behave differently. Honestly about the effect: it runs the email across a matrix of clients/devices (including dark mode and without images), finds rendering issues and gives a report with recommendations, reducing the risk of broken display, but does not guarantee identity everywhere, does not fix by itself, is relevant at the time of the test, testing ≠ sales. Honestly about access: a ready HTML email/template is needed. An important boundary: this is rendering testing; coding/fixes — 553/558; template systems — 559; content A/B tests — 552. The base price starts from 12,000 ₽ for a matrix run and a report (depends on the matrix size).
Problems we solve
- An email breaks/distorts in some clients (especially Outlook, dark mode, mobile), and you do not know before sending.
- Expecting the test to make display identical across all clients.
- Mixing the test (finds issues) and the fix (separate work).
- A misconception that correct rendering = sales growth.
What's included in the Email rendering testing service
- A matrix of popular mail clients and devices (desktop/mobile)
- Running the email through a preview service, checking dark mode and display without images
- Identifying broken blocks, distortions, responsiveness issues
- A report with issues and fix recommendations
- An honest assessment: what the test will show and what depends on the offer/content
- Honest boundaries (a test ≠ identity everywhere; a test finds, does not fix by itself; a snapshot at the time of the test; a test ≠ sales; matrix coverage is limited)
- Documentation and handover
- Review with you
What you get
- A report on the email's rendering across a matrix of clients/devices (where and what breaks)
- A clear list of issues and fix recommendations
- An honest assessment: what the test showed and what depends on the offer/content
- Honest boundaries (not identity everywhere; a test does not fix by itself; a snapshot at the time; a test ≠ sales)
How the work goes: steps
- We agree on the matrix of clients/devices, run the email
- We check desktop/mobile/dark mode/without images, record issues
- We honestly set boundaries (not identity; a test ≠ sales) and hand over the report with recommendations
Why PDV Expert
- Fixed price and timeline — no surprises on the invoice.
- Report and recommendations in plain language — clear without a technical background.
- In touch at every step and answering questions about the result.
FAQ
After the test, will the email look the same in all clients?
Not identically, honestly: clients render HTML differently (Outlook especially), dark mode is unpredictable. The test shows where and what breaks and helps bring it to 'good enough everywhere', but pixel-perfect across all clients cannot be achieved — this is a limitation of email. We honestly find issues and give recommendations.
Will you immediately fix the issues found?
The test finds issues, honestly: the fixing of the coding itself is separate work (we can do it, see 553/558). We clearly separate testing and fixes so you understand the scope; if you wish, we will do both.
Test once — and forever?
No, honestly: mail clients and their versions update, new ones appear — the test result is relevant at the time of running. With significant changes to the email/template, the test should be repeated. We honestly say this is a snapshot, not an eternal guarantee.
About the provider
The «Email rendering testing» service is provided by PDV Expert — a team specialising in «Content & acquisition». We work under contract and deliver a written report with recommendations.