Trigger the email
Submit a contact form, reset a password, place a test order — anything that calls wp_mail().
wp_mail() is intercepted and logged so you can confirm a contact form, password reset, or receipt actually fired — without ever delivering to a real inbox.
Submit a contact form, reset a password, place a test order — anything that calls wp_mail().
The message appears in the Email Log tab in seconds. Nothing left the sandbox.
Read the exact rendered HTML in an isolated frame, plus recipient, headers, and attachments.
Now you know the form actually sent — no “did it work?” guessing, no real inbox required.
wp_mail capture
SandyWP intercepts WordPress mail before it leaves. Subject, recipient, headers, and body land in the log instead of vanishing into a missing sendmail.
Isolated preview
The HTML body renders in a sandboxed frame exactly as the recipient would see it — styles, buttons, and all — with a plain-text fallback when that’s what was sent.
Never delivered
Sandbox mail is always captured, never sent to real inboxes — even with capture logging turned off. No SMTP config, no accidental emails to customers.
The rendered HTML loads in an isolated frame — the same email your users would have received. Recipient, headers, and attachments sit right beside it.
captured email · html
Email capture test
It works.
This message was sent through wp_mail and captured safely inside your sandbox.
No. Sandbox mail is always captured inside the worker and never sent to a real address — that’s true even when capture logging is switched off.
No. There’s nothing to set up. wp_mail() is intercepted automatically the moment the sandbox boots.
Yes. The Email Log tab has a one-click toggle and a clear button. Turning it off keeps mail from being delivered — it just stops recording new messages.
A reset returns the sandbox to a clean slate, including the captured email. Fresh site, empty inbox.
Free account, captured inbox, zero SMTP setup.