Features & limits
Temp Mail Inbox Limits: Time, 2 MB Size & 50-Email Cap
Understand every FreeTemp temp mail inbox limit: the 20-minute timer, 2 MB message size cap, 50-email capacity rule, and new-address rate thresholds.
By FreeTemp7 min read
Every FreeTemp temp mail inbox enforces clear operational limits to keep delivery fast, isolated, and abuse-resistant: a 20-minute default lifetime (extendable by +10 minutes up to a 60-minute ceiling), a 2 MB maximum raw email size, a 50-message storage cap per mailbox, receive-only routing with no attachments, up to 5 concurrent live WebSocket tabs per box, and a default rate limit of 10 new addresses per 10 minutes per IP connection. Knowing exactly what happens when you hit any of these boundaries prevents lost codes and wasted troubleshooting.
All Default Temp Mail Inbox Limits in One Reference Table
All thresholds below come directly from FreeTemp's mail worker configuration. Because site administrators can tune numeric defaults in the database when traffic demands it, treat this table as the standard baseline and trust on-screen notices if a value differs:
| Resource or Feature | Default Limit | Exact Technical Outcome at the Limit |
|---|---|---|
| Inbox lifetime | 20 min (+10 min steps, 60 min ceiling) | Server alarm runs deleteAll(); late emails receive 404 |
| Maximum raw email size | 2 MB per incoming message | Rejected at the SMTP edge before parsing; never stored |
| Messages per mailbox | 50 stored messages | 51st incoming email rejected (429); earlier 50 stay intact |
| File attachments | Not supported | Attachments are not stored or rendered in the preview |
| Mail direction | Receive-only | Outbound sending and replying are disabled by design |
| New address creation | 10 per IP every 10 minutes (+ Turnstile) | Extra requests return 429 until the 10-minute window slides |
| Live WebSocket tabs | 5 simultaneous sockets per mailbox | 6th concurrent tab socket receives 429 |
| Code & link auto-scan | First 60 KB of text/HTML | Prevents CPU stalls on massive HTML newsletters |
Deep Dive Into Each Operational Limit
1. Time Limit: 20 Minutes Starting, 60-Minute Rolling Ceiling
Time is the boundary you interact with on every visit. Your FreeTemp session starts at 20 minutes, and pressing +10 min extends the server alarm up to 60 minutes from the moment of your click. Once expired, the inbox is wiped permanently rather than archived—read the full clock math in how long a temporary email lasts and how extensions work.

2. Message Size Cap: 2 MB Raw MIME Ceiling and No Attachments
Standard OTP and confirmation emails weigh between 4 KB and 50 KB—less than one-fortieth of FreeTemp's 2 MB raw size cap. However, when a sender embeds high-resolution uncompressed banners or attaches a 3 MB PDF guide directly to the welcome email, MIME base64 encoding inflates the raw payload past 2 MB. To protect worker memory, FreeTemp rejects oversized messages at reception, and it never stores or displays file attachments even on smaller emails.
3. Capacity Rule: 50 Messages Stored—New Ones Rejected, Old Ones Kept
A critical detail sets FreeTemp apart from rolling-log viewers: each mailbox holds at most 50 messages, and it does not delete older messages to make room for message 51. Instead, once msg_count hits 50, the storage object refuses new incoming deliveries with a 429 capacity status while keeping your first 50 messages readable until the timer ends or you burn the box.

4. Connection Rate Limits: 10 New Addresses per 10 Minutes and 5 Live Tabs
To keep bots from exhausting domain reputation for human visitors, creating a new address runs through two lightweight guardrails:
- Cloudflare Turnstile check (enabled by default) to confirm a real browser session.
- Sliding-window IP counter allowing 10 new addresses per 10 minutes from a single connection (the temporary counter key expires within 24 hours and is never tied to message content).
Similarly, a single active mailbox accepts up to 5 concurrent WebSocket connections—more than enough for two desktop tabs, while blocking runaway scripts.
5. Receive-Only Architecture and 60 KB Smart Parser Window
FreeTemp has no "Compose" or "Reply" button. Disabling outbound mail guarantees spammers cannot hijack domains to phish third parties, which in turn keeps receiving domains healthier for legitimate users. Meanwhile, when a long HTML newsletter under 2 MB arrives, the full sanitized message still opens in the isolated preview, while automatic OTP and link extraction scans the first 60 KB so parsing stays instantaneous.
Worked Example: Diagnosing a QA Engineer's Automated Test Run
Suppose a front-end developer is manually testing localized signup templates across nine languages on a staging server using one open FreeTemp inbox:
- Tests 1–9 (18 emails total): Each test sends a 25 KB verification email and a 40 KB welcome email. All 18 arrive instantly—well under the 50-message cap and 2 MB size cap.
- Test 10 (Invoice template with a 2.8 MB embedded PDF): Nothing appears in FreeTemp. Checking fixes when a verification email is not arriving alongside the staging server's SMTP logs reveals an immediate size rejection because the raw payload exceeded 2 MB.
- Switching to hosted download links: Replacing the raw attachment with a lightweight HTTPS download link drops the email size to 18 KB, and delivery succeeds in two seconds.

Practical Steps When You Hit Any Limit
- Inbox reached 50 messages: Copy any code you still need, press Burn mailbox (or New address), and start a fresh empty inbox for your next task.
- Sender emails a large PDF attachment (>2 MB): Temporary mail cannot receive it; provide a permanent email or forwarding alias—compare options in is temporary email safe and what it protects.
- Hit the 10-addresses-per-10-minutes rate limit: Pause for ten minutes rather than refreshing rapidly; reuse your currently active inbox if time remains.
- Website asks you to send an email reply to confirm: Switch to a two-way permanent mailbox or masked-reply alias; review step-by-step reception in how to receive emails in your temporary inbox.
Common Mistakes Users Make Around FreeTemp Limits
- Deleting nothing because there is no single-message delete button—and assuming the 51st email overwrites the oldest: FreeTemp burns the entire mailbox at once rather than deleting individual rows, and once 50 messages are stored, new ones are rejected outright.
- Reloading the homepage 15 times on shared office Wi-Fi: Clicking "New address" repeatedly on a shared NAT IP burns through the 10-per-10-minutes allowance for your connection.
- Opening the same inbox across a dozen browser tabs: Exceeding 5 live WebSocket tabs triggers
429socket rejections on the extra tabs. - Waiting for file attachments to render: Even a 100 KB
.zipor.pdfattachment is stripped; look for a web download link inside the text instead.
Working With the Limits Instead of Against Them
Every cap in FreeTemp exists to keep the inbox instant, private, and reliable for short-lived tasks. Keep tasks brief, expect lightweight text or confirmation links rather than megabyte attachments, and step up to a permanent mailbox whenever a workflow outgrows a 20-to-60-minute window.
Frequently asked questions
What happens when a FreeTemp inbox reaches 50 messages—are older emails deleted?
No. Earlier messages are not deleted to free up slots. Once a mailbox holds 50 messages, new incoming emails are rejected with a 429 error until the mailbox expires or you create a new address.
Why was an email with a small PDF attachment missing its file in FreeTemp?
FreeTemp does not store or display file attachments of any size, and raw emails larger than 2 MB by default are rejected completely. Use a permanent mailbox whenever you need file attachments.
Why am I temporarily unable to create a new email address?
FreeTemp limits new address creation to 10 addresses every 10 minutes per IP connection by default to prevent automated abuse. Wait a few minutes and complete the Turnstile check when prompted.
Can I reply to an email that arrived in my FreeTemp inbox?
No. FreeTemp is strictly receive-only. Nobody—including you—can send or reply from a temporary address, which prevents outbound spoofing and abuse.