Litmus counts every client preview
Litmus
This pricing mechanic turns previewing from a simple QA step into Litmus’s main expansion lever. Each time a team checks one email across dozens of Outlook, Gmail, and Apple Mail versions, the product meters every rendering separately, so heavy users quickly hit Basic or Plus limits, then either narrow testing scope, share logins, or move up to custom pricing. That works because Litmus is strongest exactly where email teams feel the most risk, cross client rendering.
-
In practice, one test can consume a surprising chunk of the monthly allowance. Podia described an email run across many environments as burning about 100 credits at once, which pushed the team to manually uncheck clients they cared less about and share a single Basic seat.
-
That behavior is common because most teams do not need equal confidence across all clients. Beacons said it now focuses more on trickier platforms like Outlook, while skipping many versions where prior testing already built confidence, showing how pricing directly shapes QA behavior.
-
The tradeoff also helps explain Litmus’s position versus Parcel. Litmus is bought first for screenshots and rendering checks, while Parcel is preferred for writing and managing code. Teams tolerate Litmus’s pricing when the cost of a broken email in Outlook is higher than the cost of extra previews.
The long term direction is toward less punitive metering and broader platform pricing. After the Validity acquisition in April 2025, Enterprise shifted to unlimited usage and seats, which points to Litmus using previews less as a standalone toll and more as an entry point into a bigger email workflow that includes QA, monitoring, approvals, and deliverability.