Character Limit Checker

1. 01Type or paste your textThe character count and every platform check update automatically as you type.
2. 02Check which limits you fit underEach platform shows your current count against its limit, with how much room is left or how far over you are.
3. 03Add a custom limit if you need oneEnter any number to check your text against a limit not in the default list.

• Writing a post for multiple platforms at onceSee at a glance whether the same caption fits under X, Instagram, LinkedIn, and TikTok limits simultaneously, before you have to trim it differently for each one.
• Fitting a message into an SMS segmentCheck whether a text message stays within a single 160-character SMS segment, since longer messages are typically split (and billed) as multiple segments.
• Checking a YouTube video title lengthMake sure a video title stays within YouTube's title limit before it gets cut off in search results or on the video page.

• Why an emoji only counts as one character hereA character like 😀 is stored internally as two 16-bit code units (a "surrogate pair"), but it is one visible character — this tool counts it as 1, matching how most platforms count it, not 2.
• A post that fits X but not Threads-adjacent short limitsA 300-character post fits comfortably under Threads' 500-character and Instagram's 2,200-character limits, but goes 20 characters over X's 280-character limit — a common reason to trim text differently per platform.
• SMS segmentationA message of exactly 160 characters (using standard GSM-7 encoding) fits in one SMS segment; one character more typically pushes it into a second segment, which many carriers bill separately.

This tool counts Unicode code points (using JavaScript's code-point-aware string iteration), which correctly counts common emoji and non-Latin scripts as a human would expect — unlike a naive count of UTF-16 code units, which would count many emoji as 2 characters instead of 1. This is not full grapheme-cluster counting: a small number of complex, multi-codepoint emoji sequences (like some family or skin-tone-modifier emoji, built from several codepoints joined together) can still count as more than one character here, similar to how a number of real platforms also count them.

Every limit shown here is a real, published figure as commonly documented for each platform, but platforms revise these limits over time (for example, premium/paid tiers on some platforms unlock a much higher limit than the free tier). Treat the numbers here as a reliable starting point, not a permanent guarantee — if a limit is critical for your use case, verify it directly on the platform.

A standard SMS message using GSM-7 character encoding fits 160 characters in a single segment. Messages using characters outside the GSM-7 alphabet (many emoji, some accented characters, and non-Latin scripts) typically switch to UCS-2 encoding, which lowers the single-segment limit to 70 characters — this tool shows the more commonly cited 160-character GSM-7 figure as a general reference, not a guarantee for every character set or carrier.

Why does this count emoji differently from a plain JavaScript character count?

Many emoji are stored as a "surrogate pair" (two 16-bit code units) internally, so a naive `.length` count would count one visible emoji as 2 characters. This tool counts Unicode code points instead, so a single emoji counts as 1 character, matching how most platforms and most people would count it.

Are these limits guaranteed to be accurate?

They are real, commonly published figures, but platforms change their limits over time (and sometimes offer different limits for paid tiers). Treat this as a reliable reference, and verify directly on the platform if the exact limit matters for your use case.

Why is the SMS limit shown as 160, when I have heard 70 characters elsewhere?

160 characters applies to a single SMS segment using standard GSM-7 encoding. If your message uses characters outside that encoding (many emoji, some accented characters, or non-Latin scripts), it typically switches to UCS-2 encoding, which lowers the single-segment limit to 70 characters.

Is my text saved?

No. Everything is calculated in your browser; nothing is sent to a server.