Google Fi email-to-text: is msg.fi.google.com still working?
Google Fi’s @msg.fi.google.com email-to-text gateway is the most reliable survivor in 2026 and is still officially documented — but it only reaches Google Fi numbers, so it isn’t a general solution.
Last verified: July 2026
Google Fi gateway addresses
number@msg.fi.google.com— SMS
Google Fi still runs and documents an email-to-text gateway at number@msg.fi.google.com, making it the most reliable of the surviving gateways in 2026.
The catch is the same one that applies to every carrier gateway: it only delivers to numbers on that carrier. A Google Fi gateway does nothing for your recipients on Verizon, T-Mobile, AT&T, or anyone else — and it, too, can be retired at any time, as the big three have shown.
For alerts that must reach whatever phone a person happens to carry, a carrier-agnostic A2P path is the durable answer; the Fi gateway is fine only if every recipient is on Fi.
How to test if it still works
Email a short message to your own Google Fi number at number@msg.fi.google.com (replace number with the 10-digit number) and see whether it arrives. If it lands today, remember it can still stop tomorrow with no warning, exactly as the dead ones did. Don’t rely on it for anything important.
The fix
Reach Google Fi numbers the compliant way
Instead of a gateway that only works until it doesn’t, EmailToTxt delivers your alerts as real SMS over registered 10DLC — to Google Fi and every other carrier.
Your device keeps sending the same alert email. You just point it at a EmailToTxt address instead of the carrier gateway, and each alert arrives as a clean text with STOP/HELP handling built in.
Google Fi email-to-text: FAQ
- Does Google Fi email-to-text still work?
- Yes — as of 2026 Google Fi still runs and documents its number@msg.fi.google.com gateway. It only reaches Google Fi numbers, though.
- Can I use the Google Fi gateway for all my recipients?
- No. Carrier gateways only deliver to their own subscribers, so the Fi gateway reaches Fi numbers only. For mixed carriers you need a carrier-agnostic A2P path.