Mailchimp Pricing Guide for 2026

The billing model in one paragraph

Mailchimp charges for contact storage in stepped tiers, then multiplies each tier's contact limit into a monthly send allowance: ten, twelve, or fifteen times contacts depending on plan. Subscribed, non-subscribed, and unsubscribed contacts all count toward the contact limit, which makes list hygiene a billing activity from day one. Exceeding tier limits triggers add-on contact blocks billed month by month rather than throttled sending, so growth shows up as invoice lines that reward periodic tier reviews.

The multiplier design quietly favors frequent senders to small lists and punishes large dormant lists. A 2,000-contact Standard account may send 24,000 monthly emails, plenty for weekly newsletters plus automations, while a 50,000-contact archive of cold profiles pays a large storage bill for negligible sending. That asymmetry is the single most important thing to internalize before importing legacy lists, and it drives the migration math toward send-metered alternatives later in this guide.

Real contact-size examples

These Standard examples use the recurring prices in Mailchimp's marketing pricing readout. They show the plan band, not a promotional first-year discount; taxes, SMS credits, and other add-ons sit outside the row.

For a 4,000-contact audience, the $100 Standard row buys room for 48,000 sends by the 12× rule, while the vendor's band readout states a ceiling of up to 60,000 for the full 2,501–5,000 range. Budget from the published band and treat the send multiplier as the operational limit to confirm in the account selector. The key decision is whether the audience is active enough to use that allowance.

Plan tiers, verified

The free plan is deliberately narrow: up to 250 contacts, 500 sends monthly, a 250-per-day cap, one audience, one seat, basic templates, and single-step automation shapes without scheduling or advanced journeys. Exceeding the contact limit places a hold on live and test sending until upgrade or list reduction, though editing, templates, and contact collection keep working. This tier proves the editor and the signup-to-send loop, nothing more, and recent narrowings mean teams should treat it as a trial with a small ceiling rather than a home.

Essentials suits frequent senders needing support and extra power: starting tiers around 500 contacts with 10x send multipliers, up to 50,000 stored contacts, three audiences, three seats, single-email automations with flows up to four steps, A/B testing, scheduling, and 24/7 email and chat support. Standard adds deeper journeys with up to 200 flows, 12x sends, five audiences, five seats, generative AI features, and enhanced automation for growing programs. Premium serves high-scale senders with 15x sends, unlimited audiences and seats, advanced segmentation, multivariate testing, and custom onboarding. Pay-as-you-go credit blocks starting at 5,000 credits cover infrequent senders, with each send consuming one credit and credits expiring after twelve months.

Limits, overages, and the fine print

Add-on contact blocks are Mailchimp's distinctive overage mechanism: exceed contact or send limits and the account accrues extra blocks sized per plan, billed for that cycle. The practical defense is calendar discipline, reviewing contact counts against tier ceilings quarterly and archiving aggressively, since every dormant record occupies paid space. Unsubscribed contacts counting toward limits surprises nearly every importer, so suppression strategy must include archival policy, not just compliance handling.

Seats, audiences, flow steps, and template permissions gate team workflows as programs mature. One seat on free forces shared logins the moment a second reviewer joins, which undermines the approval separation our discussion scenarios require. Four-step flow caps on Essentials push multi-branch lifecycle logic toward Standard, and each such gate should be priced into the twelve-month forecast rather than discovered mid-build.

What the free tier really proves

Two hundred fifty contacts and five hundred sends prove message-market basics: a signup form, a welcome email, and two or three broadcasts to an early audience, all inside Mailchimp's famously guided interface. Non-technical founders get a genuine first newsletter without developer help, and the template library makes early mail look credible fast. That gentleness is the product's enduring strength and the reason it still tops beginner shortlists.

The honest boundary arrives with the 251st contact. Sending holds, automation gaps, and per-contact pricing geometry all push upward simultaneously, so teams should plan the exit before workflows calcify. Any program expecting billing-event triggers, agent-driven segmentation, or list growth past a few thousand engaged contacts is already standing in the wrong pricing structure, and recognizing that early saves a painful migration later.

Who Mailchimp is for

Mailchimp fits true beginners: clubs, local businesses, first-time founders, and solo creators sending their first hundreds of emails. It fits teams where non-technical stakeholders need brand familiarity to approve a vendor, and where guided setup matters more than automation depth. Short seasonal programs and event announcements with small, stable lists also fit comfortably.

Mailchimp is a weaker fit for SaaS lifecycle programs, commerce at scale, and any agent-run operation. Per-contact pricing punishes SaaS free-user accumulation, billing triggers need middleware, automation depth lags specialists, and agent access runs through conventional APIs without governed machine tooling. Growing stores should compare our Klaviyo guide, while budget generalists should read our Brevo guide.

Agent and MCP fit

Agents meet Mailchimp through its long-standing marketing and transactional APIs, a surface that is broad, documented, and entirely conventional. List management, campaign creation, template handling, and reporting all script reliably, so agents can draft campaigns, audit audiences, and pull performance data under scoped keys. There is no native MCP server, so governed agent operation needs custom tooling with proposal-and-approve wrappers around anything audience-facing.

The deeper constraint is economic rather than technical. Because unsubscribed and dormant contacts consume paid tiers, agent-built segments and archived cohorts carry carrying costs that agents cannot see unless told. Teams should expose tier headroom to agents as an explicit budget signal, require hygiene reviews before audience expansion, and keep bulk-send approval human with contact-count context attached. Single-seat free and three-seat Essentials ceilings further limit reviewer separation, so approval workflows on those tiers need compensating process rigor.

Where Mailchimp fits

Mailchimp wins beginner gentleness with guided setup and template depth that make a first newsletter achievable quickly. SaaS teams should model the cost of dormant profiles and billing-event integrations before choosing a contact-metered generalist.

The migration trigger is arithmetic: once stored contacts exceed engaged senders by multiples, per-contact billing becomes a dormancy tax that send-metered pricing eliminates. Start on Mailchimp if email is brand new and volume is tiny, but model the twelve-month contact trajectory before building automations that will need rebuilding.

Verdict and checklist

Choose Mailchimp when email is new, the list is small, and guided simplicity outweighs automation depth. Validate inside free 250 contacts and 500 sends, step to Essentials for 10x sends and support or Standard for 12x sends and deeper flows, use pay-as-you-go credits for seasonal rhythms, archive dormant contacts relentlessly, and plan the lifecycle migration before per-contact costs calcify. Re-verify every figure at Mailchimp pricing, then return to the pricing index for the full verified set.