Sending email to a phone number sounds like mixing two different systems, but it's actually a bridge technology that's been around for over two decades. When you send an email to a phone number, you're not literally emailing a phone—you're using a gateway service that converts your email message into a text message (SMS) that arrives on someone's phone.
Learn About Paying Your FGUA Bill Online →
Here's how the mechanics work: Email and SMS are fundamentally different protocols. Email travels through the internet using SMTP (Simple Mail Transfer Protocol) and arrives in inboxes. Text messages, by contrast, use the Short Message Service protocol and travel through cellular networks. A gateway sits between these two worlds, receiving your email and translating it into an SMS-compatible format, then routing it to the carrier that serves that phone number.
The process happens in seconds, but several things occur behind the scenes. The gateway receives your email, checks that the destination is a valid phone number format, removes unsupported elements (like images or complex formatting), and packages the remaining text into 160-character SMS segments. Each segment counts as one text message. If your email is longer, it may be split across multiple SMS messages, though most gateways handle this automatically.
Not all carriers support this the same way, which is why understanding your carrier matters. AT&T, Verizon, T-Mobile, and Sprint all have email-to-SMS gateways, but they operate independently. A message sent through one carrier's gateway might not work for a phone on a different carrier's network unless you use a third-party aggregator service.
Practical takeaway: Email-to-SMS isn't magic—it's a translation service. Knowing this helps you understand why some messages fail, why character limits exist, and why formatting gets stripped out.
The most critical step in sending email to a phone number is using the correct email address format. Each major carrier has its own designated gateway email address, and getting even one character wrong means your message won't reach its destination. These formats are standardized but not intuitive, so you'll need to reference them carefully.
Free Guide to Pay by Plate Illinois Billing →
AT&T customers receive messages when you send an email to [10-digit phone number]@txt.att.net. Note that this uses the full 10-digit number including the area code, with no hyphens or spaces. Verizon uses [10-digit phone number]@vtext.com. T-Mobile's gateway is [10-digit phone number]@tmomail.net. Sprint, now owned by T-Mobile, still operates [10-digit phone number]@messaging.sprintpcs.com, though customers are migrating to T-Mobile's system. US Cellular uses [10-digit phone number]@email.uscc.net, and Straight Talk operates [10-digit phone number]@vtext.com.
International carriers also have gateways, but they vary significantly. Canada's Rogers Wireless uses [10-digit number]@pcs.rogers.com. Bell Canada uses [10-digit number]@txt.bellmobility.ca. Knowing which carrier serves the recipient is therefore essential. If you don't know which carrier owns a particular phone number, you have limited options: you can ask the person directly, look at their phone bill if you have access, or use a carrier lookup tool (though these vary in accuracy and may charge fees).
The email subject line typically doesn't appear in SMS format—it's often discarded by the gateway. Some carriers may use the subject line as the message, but this is inconsistent. Your actual message content should go in the email body. Special characters, emojis, and formatting rarely survive the translation. Stick to standard keyboard characters and plain text.
Practical takeaway: Save a reference list of carrier email formats in a notes app or document. Memorizing these is impractical, but having them accessible prevents the frustration of bounced messages.
SMS has a famous constraint: 160 characters. This limit has shaped mobile communication for decades and still applies when you send email to SMS gateways. Understanding this limitation prevents messages from being split, truncated, or failing to deliver as intended.
Free Guide to Mold Removal Methods for Walls →
The 160-character limit includes everything: letters, numbers, spaces, and punctuation. This sounds restrictive, but skilled communicators have learned to work within it. "Hey, are you free Thursday night?" uses 37 characters. "Meeting moved to 2pm instead of 3pm. See you then!" uses 53 characters. These fit comfortably in one SMS segment.
When your email exceeds 160 characters, the gateway automatically splits it into multiple SMS messages. A 200-character message becomes two segments. A 400-character message becomes three. This isn't a problem per se—the recipient still receives the full message—but it means multiple charges may apply if the recipient's plan counts each SMS separately. More importantly, multi-segment messages can occasionally arrive out of order or with delays between segments, creating a disjointed reading experience.
Certain characters consume more space than others in SMS encoding. Special characters like @, #, and £ take up additional space because SMS uses different encoding schemes. The standard encoding (GSM 7-bit) handles English and common symbols efficiently. But if your message includes characters outside this set—accented letters, Chinese characters, or emoji—the entire message switches to Unicode encoding, which reduces your capacity to 70 characters per segment. This is called "UDH (User Data Header) encoding" and catches many people off guard.
Formatting like bold, italics, line breaks, and links don't survive the email-to-SMS conversion. When you hit send on an email with multiple paragraphs, the gateway collapses everything into one continuous string of text. Links become plain URLs, and visual structure disappears. This is why your message should be written as plain text from the start.
Practical takeaway: Write your message as if it were a text first. Keep it under 160 characters if possible. If you must go longer, write it assuming it will arrive as multiple messages, and order your points accordingly so they make sense if delayed.
Not everything you can do in a regular email will function when you route a message through an SMS gateway. Knowing what survives the conversion and what gets stripped away helps you craft messages that land exactly as intended.
How to Delete Your Fitbit Account Guide →
Plain text survives. Numbers survive. Most standard punctuation (periods, commas, question marks, exclamation points) survives. Line breaks—the ones you create by pressing Enter—sometimes survive depending on the carrier, but many gateways collapse them. Spaces survive, and multiple spaces are preserved (though some carriers may compress them). This is the reliable foundation.
Images, attachments, and embedded files do not survive. If you send an email with an image attachment to an SMS gateway, the image is discarded and only the text message content arrives. HTML formatting does not survive—all the colored text, font sizes, and styled elements disappear. Tables, if you're trying to send one, get converted to plain text in whatever way the gateway interprets it, usually rendering it unreadable. Links become plain text URLs, and mailto: links become useless text strings.
Signatures on emails sometimes arrive as part of the SMS (wasting your 160 characters) and sometimes get stripped, depending on the gateway. If you're using an email client, remove your automatic signature before sending to a phone number, or keep it extremely short. Special characters like ™, ®, and © may not render properly. Smart quotes (the curved ones your word processor inserts) sometimes convert to straight quotes, sometimes cause encoding errors.
Scheduling—the ability to schedule an email to send at a future time—works on your end with most email providers, but some SMS gateways have delays. You might schedule an email to send at 2 PM, but it may not reach the SMS gateway until 2:05 PM or later, introducing unpredictable timing. If the recipient's phone is off, has no signal, or their account has issues, there's no automatic retry—the message simply fails silently or bounces.
Read receipts and delivery confirmation are not standard with SMS gateways. Your email client might request a read receipt, but SMS doesn't support this, so you won't know if the message was read. Some advanced services offer
This guide is for general information only and is not medical, financial, legal, or other professional advice. For decisions specific to your situation, consult a qualified professional. See our Editorial Policy.