SMS Character Counter

SMS encoding determines how many characters fit in a single text message and directly impacts your messaging costs. Standard GSM-7 encoding fits 160 characters per segment using a 7-bit character set that includes A-Z, a-z, 0-9, and basic punctuation. When your message includes emojis, accented characters (café, ñ, ü), or certain special characters (~, ^, curly braces), the entire message switches to UCS-2 Unicode encoding, which only fits 70 characters per segment. A single emoji can more than double your per-message cost by cutting your character limit in half.

Multi-part SMS messages add complexity. When messages exceed single segment limits, carriers split them into multiple segments and use concatenation headers (invisible metadata) to reassemble them on the recipient device. These headers consume characters, reducing GSM-7 messages from 160 to 153 characters per segment, and Unicode messages from 70 to 67 characters per segment. This means a 161-character GSM-7 message requires 2 full segments (billed as 2 SMS credits), not 1.01 segments. Understanding these thresholds prevents budget surprises when scaling campaigns.

Hidden Unicode characters are the silent budget killer in SMS marketing. Microsoft Word and many text editors insert fancy quotes (“ ” instead of "), en-dashes (– instead of -), and other Unicode punctuation that looks identical to GSM-7 characters but triggers expensive Unicode encoding. A single smart quote copied from a Google Doc can turn your 150-character promotional message from 1 segment ($0.01) into 3 segments ($0.03), tripling your cost per recipient. For a 100,000 recipient campaign, that is a $2,000 mistake from one invisible character.

International SMS campaigns require special attention to encoding. While English messages typically use GSM-7, Spanish (¿, ¡, ñ, á, é), French (à, è, ê, ç, œ), German (ä, ö, ü, ß), and other languages often include accented characters that force Unicode encoding. A bilingual message with “café” instead of “cafe” drops from 160 to 70 characters per segment. For global campaigns, test messages in all target languages and consider ASCII-only alternatives where culturally appropriate, or budget for higher segment counts when accents are essential.

FoneSwift SMS Counter provides real-time encoding detection and visual Unicode highlighting so you see exactly which characters are costing you extra. Hover over amber-highlighted characters to identify Unicode culprits. Remove unnecessary emojis, replace fancy quotes with straight quotes, and swap accented characters where possible. Our tool shows remaining characters before the next segment boundary, helping you optimize every message. Link directly to our Bulk SMS Cost Calculator to estimate total campaign costs based on your optimized segment counts. Save thousands on SMS spend by understanding encoding before you send.