Parcel for coding, Litmus for testing
James Kupczak, email and marketing automation specialist at MedBridge, on email code editors
This workflow shows that email teams often split writing from validation, and the editor that wins is the one that makes raw HTML fastest to change. In practice, Parcel is where specialists want to type, inspect, and fix code, while Litmus remains the place some teams standardize on for previews, proofs, and cross client checks. That is why copying code from Parcel into Litmus is common rather than contradictory.
-
James uses Parcel for freelance jobs because it is faster for one off builds. He can click a visual element and jump to that exact code, run accessibility checks, and work in an editor that feels closer to VS Code. He still pastes into Litmus when a client’s approval workflow lives there.
-
The same division shows up at larger teams. At Figma, Parcel is the main workspace for building and collaborating on marketing emails, while Litmus is kept mainly for inbox previews and for separate users like engineering testing transactional layouts. Litmus is useful, but not the day to day coding home.
-
Across the market, Litmus is generally treated as a testing product with editing attached, while Parcel is treated as a coding product with testing attached. That difference matters because email developers spend most of their time making tiny HTML fixes, not just checking screenshots across Outlook and Gmail.
The market is moving toward tools that own more of the actual email creation workflow, not just the final preview step. As teams build reusable components and tighter review flows, testing will become a feature inside the editor, and the product with the better developer experience will capture more of the daily work and more of the budget.