Litmus is a well-liked tool that buyers still leave. None of the leavers here describes rendering quality as the reason for leaving — one still calls it a great platform. Instead they describe price increases, overlap with a deliverability platform that renders and previews email too, or a use case they no longer needed. Some buyers attribute the price increases to Litmus’s acquisition by Validity. For the email platform decision around it, see what email-platform buyers wish they’d known.
The alternatives, by what they are
Every destination buyers name, sorted by what it is. The top lane is a consolidation move rather than a like-for-like swap: the destination is a deliverability platform that added rendering.
Where buyers go
Mostly to one place. Price appears repeatedly in the departures, while several Inbox Monster moves also offer the chance to consolidate rendering and deliverability.
Folded into the deliverability platform — the most common exit
Most departures went here, and the reasons repeat. One buyer says simply “Price was an issue.” Another, consolidating to reduce technical debt, says “Validity jacked up their prices. They haven't made a lot of changes as far as improvements and optimization on the platform” — while still calling Litmus “a great platform.” Buyers who have moved describe Inbox Monster as “much more advanced”, one adding that “In terms of pricing also, they were pretty good”, and another says it cut their email preview cost substantially.
No head-to-head published yet
Not a departure yet, but the same shape. A buyer running both tools says “we've got Inbox Monster and Litmus that essentially do the exact same thing” and plans to decide which to keep. They put the change in their own rating down to ownership: “because they were acquired by Validity, their rating for me has gone down.”
No head-to-head published yet
Everyone else
A like-for-like move, prompted by price: “they raised their prices dramatically again, prompting us to do some research and find Email on Acid to actually be better for what we're trying to do anyway.” Too few buyers rate Email on Acid to publish a number.
No head-to-head published yet
One team used Litmus mainly to build HTML email templates, found another way to do that, and concluded “Litmus was not that necessary anymore.” The same buyer still valued features such as email timers and dark-mode tracking.
No head-to-head published yet
Across the set, the pattern is consistent and small: price is the trigger most departures name, and consolidation into a deliverability platform is where most of them land. None of the leavers describes Litmus failing at rendering, which is the job it was bought for.
What lower-rating Litmus buyers complain about
There are few of them, and price leads. Only a handful of buyers rate Litmus 6 or below, too few to compare themes between rating bands, so this section also draws on buyers rating it 7. Price is the complaint that comes up most: one says “It's just their pricing model with Validity has now increased a lot”, another that “The more device previews you utilize, the higher the cost”, and a buyer who is leaving that “Their pricing is just way higher than it was when we brought them in.”
Then limits around the edges of the core job. Buyers who otherwise rate it well name gaps rather than failures: “They don't have the integrations that we need”; the analytics “are not that great”; it is “not great in terms of the possibilities it provides for personalization”; and a single-user account that makes it hard to share. One lower rater used it for template building and found that “extremely manual.”
Rendering is not the complaint that dominates these interviews. The recurring complaints instead concern price and capabilities around the core rendering job, including integrations, analytics, personalization and account structure.
Want this read against your own stack?
Get my read →When does staying on Litmus make sense?
The interviews do not settle staying as a rule, but two themes appear in positive Litmus commentary.
Rendering across devices and email clients. One buyer describes the value directly: “Litmus will essentially test across all phones, all tablets, all software, how things will look.” Another calls it “a pretty key add-on for us”, and one team adopted it “because it was the industry leader in Email Marketing testing.”
A proofing workflow that extends beyond the email team. Buyers value the review workflow as much as the rendering: “It's very easy to provide feedback, to resolve feedback, and to handle that proofing process in Litmus.” Buyers also note that team members who are not HTML experts can use it.
Price and tool overlap appear more clearly in the departure evidence than complaints about the core rendering job. Our read — ours, not a buyer’s — is that a useful renewal question is whether another platform already in the stack covers enough of the rendering workflow to make a separate Litmus subscription worthwhile.
Common questions
Why do buyers leave Litmus?
Price is the reason leavers name most, while consolidation and a use case no longer being needed also appear in the departure evidence. Litmus rates around 8/10, and buyers scoring it 8 or better outnumber those scoring it 6 or below by more than five to one. The buyers who left describe price rises — some attribute them to Litmus's acquisition by Validity — and a chance to consolidate onto a deliverability platform that now does email rendering too. One leaver still calls it a great platform. One buyer dropped it because the use they had for it was no longer needed.
What do buyers replace Litmus with?
Mostly Inbox Monster. Most of the departures in these interviews went there. It is a deliverability platform that now covers rendering and previews as well, so for a team that wants both, one tool can replace two. One buyer moved to Email on Acid after a price increase and found it better for what they needed, and one dropped Litmus with no replacement. Inbox Monster rates around 8/10; Email on Acid has too few buyer ratings to publish a number.
Is Inbox Monster a good alternative to Litmus?
The buyers here who made that move describe it positively, and on price as much as on features: one calls it much more advanced, another says pricing was pretty good as well, and a third says it cut their email preview cost substantially. Both tools rate around 8/10 across the corpus. What these migrations clearly establish is consolidation: buyers can put deliverability and rendering in one platform. The interviews here do not isolate whether they consider Inbox Monster's rendering itself better than Litmus's.
What do buyers like about Litmus?
Rendering and proofing are the clearest positives in these interviews. Buyers rating it 8 or better describe seeing how an email renders across phones, tablets and email clients before it goes out, a proofing workflow that is easy to share with stakeholders, and a tool that non-technical team members can use. One adopted it as the industry leader in email testing. The complaints from buyers who still rate it well are about limits around the edges — analytics, personalization previews, integrations and seat limits — and about price.
Get this research made for your stack
Deciding whether to keep a separate email-testing tool or fold rendering into your deliverability platform? Do a 15-minute interview about your email stack and your team, and get a personalized read.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.