149 countries · crypto-native · email-only signup

Send a Text From Email to a Phone

Emailing a text used to be a reliable trick: address a message to the phone number at the carrier's own domain and it arrived as an SMS. Much of that plumbing has been quietly switched off.

Here is what survives in 2026, how to check whether your carrier still runs a gateway, and the browser route that works whether or not it does.

Email signupNo IDCrypto pay
from $0.004per message
149countries
minutesto first message
6cryptocurrencies
TL;DR
  • Several major US carrier email-to-SMS gateways were retired across 2024 and 2025. Verify yours before you rely on it.
  • The address lists circulating on forums and cheat sheets were not updated, so treat every one of them as unverified.
  • Even a live gateway offers no delivery receipt, truncates long bodies and passes through spam filtering.
  • Mail-client rules and SMTP scripts can still automate sends through whatever gateway your carrier keeps alive.
  • SMSRoute is the browser alternative: email-only signup, from $0.004 a message, delivery status shown on screen.

Carrier email-to-SMS gateways in 2026

The classic method builds an address from the destination number plus the carrier's own domain, in the shape of 5551234567@example-carrier.net. Mail sent there arrives on the handset as a text. It cost nothing and needed no account anywhere, which is why it spread so widely.

That was true for years and it is no longer safe to assume. Several major US carriers retired email-to-SMS and email-to-MMS gateways across 2024 and 2025, and the address lists that circulate online were not revised. An address that worked in 2021 may bounce today, or worse, accept the mail and drop it without a word.

One check is reliable: ask your carrier directly, or read its current support pages for the line you are sending to. Treat any third-party list, including whatever sits at the top of a search page, as the starting point for that question rather than the answer to it.

Why the gateways became unreliable

Even at their healthiest the gateways behaved like email, because that is what they were. Messages crossed spam filters on the way in, and a filter that quietly discarded one gave no signal to the sender at all.

Length was the second problem. Long bodies were truncated at the gateway, HTML formatting was stripped, and attachments either vanished or pushed the message down an MMS path with different rules again. A signature block and a quoted reply could eat the character budget before the actual sentence arrived.

The third problem mattered most: there was never a delivery receipt. A gateway send is fire and forget. You never learned whether the phone received anything, which made the method fine for a reminder to yourself and poor for anything that had to land.

Automating sends from your email client

If your carrier does still publish a working address, ordinary mail clients can drive it with no extra software. Save the gateway address as a contact so you are not retyping it, then let rules do the routing: a filter that forwards flagged mail to that contact turns an inbox event into a text.

Scripts are the step up. Anything that can talk to an SMTP account, from a scheduled task to a monitoring tool, can address mail at the gateway and fire on a timer. Keep the body short, keep it plain text, and strip the signature block.

Every such setup inherits the same weakness. The automation is only as alive as the gateway beneath it, and that gateway can be switched off without notice. Build it so failure is visible, and pair it with a route that reports back when the message actually matters.

The three routes side by side

Set against each other, the three options split on one question: do you need to know whether the message arrived?

email to SMS, three routes compared
RouteCostDelivery statusInternational reachStill works?
Carrier gatewayFreeNoneMostly domestic if at allVerify with your carrier
Mail client automationFree, rides the gatewayNoneSame as the gatewayOnly while the gateway lives
Browser senderFrom $0.004Shown on screen149 countriesYes

Gateway availability changes without announcement, so confirm the current address with your carrier before building anything on it. Compiled 2026-07-26.

The bottom row is where SMSRoute sits. It costs money per message rather than nothing, and in exchange it reports back. Signup is an email address, the balance is topped up with crypto, and there is no ID check at any stage.

The browser route: type it in a web sender

A web sender removes the question entirely. Open a page, paste the destination number, type the body, submit. The provider injects the message into carrier networks from its own numbers, so nothing depends on your carrier keeping a mail gateway running.

Pricing starts at $0.004 per message, coverage runs to 149 countries, and BTC, ETH, USDT, XMR, LTC and SOL are accepted for the balance. Delivery status appears on screen once the message leaves, which is the single thing no gateway ever gave you. The same ground is covered from a different angle in texting from a computer and sending SMS without a number.

The limit is real and worth stating up front: the route is send-only. Replies do not come back and no verification code can be received on it, which rules it out for two-factor setups. Decide by what a silent failure costs you. A dropped birthday reminder is an annoyance; a dropped delivery window is a phone call you now have to make anyway.

Read this first: do not copy a carrier gateway address from an old list and assume it works. Several were retired across 2024 and 2025. Confirm the current address with the carrier that serves the destination number.

Frequently asked questions

Can I still email a text using number@carrier addresses?

Some gateways may still run, but several major US carriers retired theirs across 2024 and 2025. Verify the exact address with your carrier before depending on it, and do not trust an undated list.

Why did my email-to-text messages fail silently?

Spam filtering, hard length limits and the total absence of delivery receipts were the standard failure modes of carrier gateways. A dropped message looked identical to a delivered one.

Is email client automation still useful?

Yes, where a working gateway exists. Rules and SMTP scripts can send without opening a separate app, but they inherit every gateway limitation, including silent failure.

What does a web sender give me that gateways lack?

Delivery status you can see, predictable international reach across 149 countries, and no need to hunt for a carrier domain that may already be switched off.

How does SMSRoute fit a send-from-email workflow?

You sign up on an email address alone with no ID check, top the balance up with crypto, and send from the browser from $0.004 per message. It is send-only, so replies are not supported.

An email address is the only thing you enter. Free test credits send a real text before you pay.

Send your first textor see per-text prices