How Limitora Verifies Character Limits

Every limit on this site is sourced, checked and dated. Here's exactly how.

Where our numbers come from

Every limit published on Limitora traces back to one of three primary sources, in order of preference:

1. Official developer documentation — e.g. Meta's Graph API reference, X's API documentation, Google Ads' character limit specs. This is the ground truth wherever a platform publishes it.
2. Official help center or creator resources — used when a limit isn't documented in a developer API but is stated in the platform's own consumer-facing help pages.
3. Direct testing — for limits neither of the above states explicitly (e.g. exact visible-truncation pixel points in a feed), we test directly in the live product and record the observed behavior, noting it as tested rather than officially documented.

We do not source limits from other character-counter websites, forums, or unverified blog posts. If a limit can't be confirmed against a primary source, we don't publish it.

Technical maximum vs. visible truncation point

Most platforms enforce two different numbers for the same field, and most character-counter tools only report one of them:

• The technical maximum — the hard character limit the platform's input field will accept before rejecting further text.
• The visible truncation point — the shorter length at which the platform's feed, search result, or preview actually cuts the text off with a "more" link or ellipsis, before a user takes any action to expand it.

Instagram's caption field technically accepts 2,200 characters, but the feed truncates visible text at roughly 125 characters before showing "more." A tool or article that only states "2,200 characters" is technically correct but practically unhelpful — it doesn't tell a creator what actually determines whether their hook gets read. Wherever this gap exists, Limitora reports both numbers, not just the larger one.

Update cadence

Platform character limits change more often than most people assume — usually without a formal announcement. Our review cycle:

• Monthly: every tool and cheat sheet entry is re-checked against current official sources.
• On report: if a reader flags a discrepancy via our contact form, we verify and correct within 2 business days.
• On platform announcement: when a platform publicly announces a limit change, we prioritize updating the affected page ahead of the regular monthly cycle.

Every article on Limitora displays a "Last updated" date. Every tool page reflects the limit as of that same verification cycle. If you notice a mismatch between what's published and what a platform currently enforces, please tell us — platforms do change these values without notice, and reader reports are one of our fastest correction paths.

What we don't do

• We don't publish estimated or "approximate" limits without labeling them as such.
• We don't copy limits from other character-counter sites — every number is independently re-verified against a primary source.
• We don't fabricate usage statistics or claim survey data we haven't actually collected. Any illustrative numbers used for design purposes elsewhere on the site are clearly non-factual UI elements, not claimed research findings.

Corrections

Found an outdated or incorrect limit? Use our contact form with the specific page and field — we investigate every report and correct confirmed errors promptly, crediting the report where the reader wants credit.

Related

See our full character limits cheat sheet for every verified limit in one place, or read more about Limitora.