Social Media
Social Media Character Limits
AI Summary
Social platforms enforce character limits on captions, bios, and titles. Hard maximums and early truncation are different problems. Use this hub for orientation and methodology, verify live limits in each app, and check length with QTT tools before you post. Registry numbers are orientation unless marked verified.
Key Takeaways
- Most social fields are character-limited, not word-limited.
- Hard maximums and “see more” truncation are different constraints.
- Put the hook and call to action before truncation points.
- Platform numbers in QTT are orientation until verified in-app.
- Count with Character Counter or field checkers, then confirm in the composer.
Platform orientation from the QTT limits registry
Values come from QuickTextTools’ limits registry (last reviewed 2026-08-08). Rows marked orientation are consolidated guidance — not real-time platform APIs. Confirm in the live app or SERP before publishing.
| Field | Value | Type | Status |
|---|---|---|---|
YouTube video title YouTube | 100 | Hard max (oriented) | orientation |
YouTube title display caution YouTube | 60 | Soft display / QTT caution | orientation |
Instagram caption Instagram | 2200 | Hard max (oriented) | orientation |
Instagram caption feed truncation Instagram | 125 | Truncation orientation | orientation |
Instagram bio Instagram | 150 | Hard max (oriented) | orientation |
Instagram username Instagram | 30 | Hard max (oriented) | orientation |
TikTok caption TikTok | 2200 | Hard max (oriented) | orientation |
X (Twitter) standard post X | 280 | Hard max (oriented) | orientation |
X (Twitter) bio X | 160 | Hard max (oriented) | orientation |
X (Twitter) display name X | 50 | Hard max (oriented) | orientation |
Search title display guidance Google SERP | 60 | Soft display / QTT caution | orientation |
Search meta description display guidance Google SERP | 160 | Soft display / QTT caution | orientation |
Social posts fail for a boring reason: the ending never appears. Limits and truncation hide calls to action, links, and punchlines. This page is the Character Limits hub: methodology, categories, verification policy, and paths into QTT tools—not a dump of every number on the internet.
Hub vs spoke: For Instagram / Facebook / TikTok / X field numbers, use the dedicated table spoke Character Limits for Instagram, Facebook, TikTok, and X. This hub explains how to think about limits and where to check them.
Hard Limits vs Truncation vs QTT Recommendations
- Hard maximum (platform) — the app may block or cut text past a number
- Truncation — the feed shows only the first lines, then “more”
- QTT recommendation / soft display — writer guidance (for example ~60 on YouTube titles) that is not the same as a hard platform rule
Stay under the max, and still write the first lines as if that is all anyone will read.
Platform & Use-Case Map
- Social captions & bios — start with the four-platform field table; craft help for Instagram captions
- Video titles — length check with the YouTube Title Length Checker; craft in YouTube titles
- Search snippets — soft display guidance in Meta Tag Generator and Meta Title Preview; craft in meta descriptions for SEO
- Any paste job — Character Counter (True Count) for honest multi-mode length
Verification & Update Methodology
- QTT stores shared numbers in a limits registry with status (
orientation/verified/unknown) and last-reviewed dates. - Orientation values consolidate prior QTT guidance so pages do not contradict each other. They are not live API feeds.
- Before a high-stakes post, open the real composer or YouTube Studio / SERP preview and confirm.
- Registry last reviewed for this hub cycle: 2026-08-08.
Pre-Post Length Workflow
- Draft without staring at the meter.
- Put the hook and CTA near the top.
- Count with the right QTT tool for the field.
- Trim fillers and extra spaces if over budget (Remove Extra Spaces / Text Cleaner).
- Paste into the real composer and confirm the live count.
- Publish only after the visible preview still makes sense.
Examples
Example 1 — CTA behind “more”
The link sat at the end and disappeared. Move the CTA into the first lines, then recount.
Example 2 — Bio overflow
A bio that looked fine in Notes failed on save. Spaces and emoji filled the budget—True Count modes help explain surprises.
Example 3 — Dirty paste
Copied caption brought extra spaces. Clean, then count.
Common Mistakes
- Ignoring truncation because you are under the max.
- Treating a soft “optimal” number as a hard platform rule.
- Trusting last month’s screenshot without checking.
- Leaving the CTA at the end.
- Skipping the in-app confirmation.
Conclusion
Use this hub for orientation and workflow. Use the four-platform spoke for field numbers. Check length with QTT tools, then verify live—because platforms change.
Frequently Asked Questions about Social Media Character Limits
What are social media character limits?
They are maximum lengths platforms set for captions, bios, titles, and related fields. Exact numbers change over time, so verify in each app.
How do I check my character count before posting?
Paste the text into the Character Counter or a field-specific checker (such as the YouTube Title Length Checker), then paste into the real composer to confirm the platform’s meter.
Do spaces count?
Yes. Spaces usually count toward character limits.
Do emojis count as characters?
Yes. Counting systems differ (code points vs UTF-16). Use True Count modes on the Character Counter when emoji length looks surprising.
What is truncation?
Truncation hides the end of a post behind “more” or an ellipsis even when you are under the hard maximum.
Should I trust a third-party limit table forever?
No. Treat published tables as orientation. Platforms change composers and caps—confirm in the live app when the post matters.
Where are Instagram, Facebook, TikTok, and X numbers?
Use the dedicated Instagram, Facebook, TikTok, and X limits guide linked below for the field table. This hub focuses on methodology and navigation.
Does QTT update limits in real time?
No. Limits live in a maintained registry with last-reviewed dates. They are not pulled live from each platform’s API.