The MailHog alternative for Mac

MailHog hasn't had a release since 2020 and Homebrew no longer ships it. See how Mailbox compares, and switch in a minute by keeping port 1025.

For years, MailHog was the default answer to “how do I catch emails in development?”. It still runs, but it has stopped moving: the last release, v1.0.1, shipped in August 2020, its maintainer wrote in 2023 that he no longer has time to maintain it, and Homebrew removed the formula in April 2026, so brew install mailhog no longer works. Its prebuilt binaries and Docker image are Intel-only, so on Apple Silicon the container runs under emulation.

If you develop on a Mac, Mailbox does the same core job as a native app — and adds the checks MailHog never had.

Mailbox vs MailHog at a glance

MailHogMailbox
What it isGo binary or Docker container with a web UINative macOS app
Actively maintainedNo — last release in 2020Yes
Apple SiliconPrebuilt binaries and Docker image are Intel-onlyNative
InstallDocker or go installMac App Store
HTML, text, headers, attachments✓✓
HTML compatibility check✗✓ 300+ HTML/CSS features across 22 email clients
Mobile and dark mode preview✗✓
Separate inboxes per projectOne inbox per running instance✓ One server and port per project (Pro)
SendGrid, Postmark, Resend, Mailgun, Brevo, Mailtrap API mocks✗✓ (Pro)
Provider-style webhooks (delivered, opened, clicked)✗✓ (Pro)
Release or forward to a real SMTP server✓✓ (Pro)
REST API✓✓ (Pro)
Chaos testing✓ (“Jim”)✗
Emails kept after restartIn-memory by default✓ Stored on disk
Runs on Linux, Windows, in CI✓✗ macOS only
PriceFree, open source (MIT)Free tier, optional Pro upgrade

What Mailbox adds

It’s a Mac app, not a container. Mailbox lives in your menu bar, can start its servers when you log in, and keeps captured emails on disk, so they’re still there after a restart. There’s no Docker daemon to run and no browser tab to keep open.

It tells you whether your email will render. The HTML compatibility check scans each message against caniemail data — over 300 HTML and CSS features across 22 email clients — and shows which ones Outlook, Gmail or Apple Mail won’t support. The mobile preview renders the email at real phone viewport sizes, and the dark mode preview shows how it looks with a dark background.

It covers API-based sending too. Many apps no longer speak SMTP and call SendGrid, Postmark or Resend over HTTP instead. Mailbox Pro accepts the same requests on a local endpoint, so you change a base URL instead of your code, and it fires delivered, opened and clicked webhooks in each provider’s own payload format.

One inbox per project. With Pro, each app gets its own server on its own port, and its emails never mix with another project’s.

Switch from MailHog in a minute

MailHog listens on port 1025. Give your Mailbox server the same port and your app configuration doesn’t need to change at all:

  1. Open Mailbox and edit the server (or add one) to use port 1025.
  2. Start it and stop MailHog — remove the mailhog service from your docker-compose.yml if you used one.
  3. Send an email from your app. It shows up in Mailbox.

If your app itself runs in Docker and used mailhog as the SMTP host, change the host to host.docker.internal. Framework-specific steps are in the setup guides.

When MailHog-style tools are still the right choice

Mailbox is a Mac app, so it can’t run in a Linux CI pipeline or on a shared staging server. For those, use a cross-platform catcher — and since MailHog is no longer maintained, that should be Mailpit. Many teams use both: Mailpit in CI, Mailbox on their Macs.

More comparisons