JavaScript’s .length tells you how many UTF-16 code units a string contains—not whether a social API will accept it. In Bluesky’s official example, the family emoji 👨👩👧👧 has a JavaScript string length of 25 but a grapheme length of 1. Other platforms use their own counting rules, and APIs may impose byte or indexing constraints too. A generic counter can help flag likely problems, but only the target platform’s documented rules and validation can settle whether a post fits.
What does JavaScript .length actually count?
JavaScript strings are sequences of UTF-16 code units, and .length reports the number of those units. A code unit is not necessarily a complete Unicode character: some code points are represented by a pair of UTF-16 units, and a displayed emoji can be built from several code points joined together.
As an Amazon Associate I earn from qualifying purchases.
That makes “character” ambiguous. It can mean a storage unit, a Unicode code point, a user-perceived symbol, a platform-defined weighted unit, or a byte in an encoded string. Those measures answer different questions.
Free tools Windows power users keep installed
One-click scans. No signup required.
- UTF-16 code unit: The unit JavaScript counts with
.length. Some Unicode characters need two units. - Unicode code point: A Unicode value. Counting code points avoids splitting surrogate pairs, but a sequence of several code points may still appear as one symbol.
- Grapheme cluster: A sequence that approximates one user-perceived character. A family emoji joined from several code points can be one grapheme cluster.
- Weighted platform count: A platform-specific measure that can assign different weights to different text, rather than counting each visible symbol equally.
- UTF-8 byte: A unit of encoded data. Byte limits and byte offsets are not interchangeable with code units, code points, or grapheme clusters.
For example, a code-point count can differ from both the UTF-16 length and grapheme count of the same emoji. None of these measures is a universal substitute for a platform’s own rule.
#1 Best Overall
How documented social API rules differ
The following examples demonstrate why a single cross-platform “character limit” counter is misleading. They describe specific API or documentation behavior, not a guarantee that every consumer-facing composer behaves identically.
| Platform | Documented counting or limit detail | What to verify |
|---|---|---|
| X | X’s developer materials describe a weighted post-counting system. Some glyphs count as more than one; the exact treatment is defined by the twitter-text configuration. | Use the documented counting algorithm and configuration for the API and post field you target. A plain JavaScript length is not a replacement. |
| Mastodon | The official documentation gives a default post limit of 500 characters. For a mention, the username counts, but the domain does not. | The instance API exposes configuration, so check the target server rather than assuming it uses the default. |
| Bluesky | The official RichText tutorial reports the family emoji 👨👩👧👧 as .length 25 and graphemeLength 1. The tutorial also describes rich-text facet ranges as UTF-8 byte offsets into the post text. |
Keep grapheme counting distinct from facet indexing. A byte offset identifies a position in encoded text; it is not a visible-character count. |
These are not interchangeable platform limits. The Mastodon figure is a documented default, X’s count is weighted, and Bluesky’s example illustrates distinct string and grapheme measures. The Bluesky facet offset detail is about indexing, not evidence of a post-length limit.
Rank #2
- BOOST YOUR PRODUCTIVITY - This undated weekly productivity planner notepad focus on the important work and get organized. Weekly to do list notepad allowing you to categorize and prioritize your tasks effectively. Whether you're a small business owner, project manager, freelancer, academicians or master multitasker, the weekly to do list pad will be your new favorite daily office productivity tool.
- UNDATED WEEKLY PLANNER - This weekly planner start any time with 54 weeks, Weekly planner notebook has plenty of space to write your goal plan, work plan, student plan or personal schedule, keep track of priorities, and write notes on the back. This versatile planner allows you to stay organized in 2026, 2027, or even as far ahead as 2028!
- FEATURES - Weekly Theme and Highlights for at-a-glance planning Top 3 Priorities for the week 6 Focus Areas to segment and list tasks for goals, projects, or clients Daily Tracker for healthy habit-tracking and routine-tracking.
- HIGH QUALITY - This weekly desk planner size of 8.5" x 11", it offers ample space for writing and planning your tasks, just the perfectly size to fit in your backpack. Is used to high quality 100gsm pure white paper, elastic band and a back pocket for extra space.
- FUNDTIONAL DESIGN - This weekly deskpad planner will completely change how you structure your work: by segmenting your tasks by area and tracking the most important details, you'll feel less scattered and more organized.We believe in helping you be fulfilled with your life and productive at the same time by using a weekly to do list notepad.
Why a post can fail even when .length looks safe
There are two different mismatches behind the claim that .length “lies both ways.” For a joined emoji sequence, the UTF-16 count can be much larger than the grapheme count. Conversely, a platform’s weighted rule—or a separate API byte constraint—can make a string unacceptable even when a naïve code-unit counter appears to leave room. Neither direction applies to every emoji or every platform; the exact sequence and platform rule matter.
Recommended Free Tools
Normalization can also matter if an application changes the text between counting and submission. Combining marks may be represented as separate code points or as part of a precomposed character, and transformations can change string length or byte offsets. Do not normalize or rewrite a post merely to make a counter pass unless the target platform’s documentation calls for that behavior; changing the text can also invalidate positions used for annotations or facets.
Rank #3
- Unleash Your Productivity Potential - Our weekly to do list notepad provides a complete system for managing your tasks. It includes a checklist, a top priority section, a low priority section, and a follow-up section, allowing you to categorize and prioritize your tasks effectively.
- Undated Weekly Planner - Embrace the freedom of an Undated Weekly Planner with 52 weeks of undated planning pages. No more wasted spaces or skipped dates – start your planning journey exactly where you left off, any time you want. This versatile planner empowers you to master your schedule for the entire year.
- Functional Design - Our notepad features premium quality covers and twin-wire binding, providing durability and flexibility for smooth page-turning. The sturdy cardboard backing ensures stability on any surface, making it a reliable companion for your daily tasks.
- High-Quality Design - Our weekly desk planner is crafted with attention to detail, using premium quality 60-pound smooth white paper and a sturdy chipboard backing. Measuring at a convenient size of 11 X 8.5 inches, it offers ample space for writing and planning your tasks. The clean and elegant design adds a touch of sophistication to your workspace.
- Versatile and Long-Lasting - Our desk planner is suitable for various uses, including office, home, school, or personal organization. It is made with high-quality paper to ensure durability throughout the year, making it a reliable companion for all your planning needs.
How to validate post text safely
- Identify the exact field and destination. Determine whether you are validating a post body, caption, title, or another field, and which platform, API version, account tier, and—on Mastodon—server will receive it.
- Use that destination’s documented algorithm. Implement a platform-specific adapter rather than treating
.length, code-point count, or grapheme count as a universal rule. For X, follow the weighted-count documentation and its specified twitter-text configuration. - Keep estimates separate from acceptance. A local preflight counter can provide a useful warning, but label it as an estimate unless it implements the exact documented rule for the target. Do not substitute a grapheme count for a weighted platform count.
- Submit the final text and handle validation errors. The API’s response is the acceptance check. If it rejects a post, surface the platform’s error and let the user edit the text; do not silently truncate it, since that can change meaning, links, mentions, or annotations.
- Calculate offsets against the final string. If an API feature uses byte offsets, compute them according to that API’s specified encoding and against the exact text being submitted. Do not derive byte positions from grapheme or JavaScript code-unit counts.
For local diagnostics, JavaScript can show several distinct counts side by side. This example is not a platform validator:
const text = "👨👩👧👧";
const codeUnits = text.length;
const codePoints = [...text].length;
const graphemes = [...new Intl.Segmenter(undefined, {
granularity: "grapheme"
}).segment(text)].length;
const utf8Bytes = new TextEncoder().encode(text).length;Here, the variables represent UTF-16 code units, code points, grapheme clusters, and UTF-8 bytes respectively. They are useful for understanding what a string contains, but none should be treated as a platform’s limit unless that platform documents that exact measure and counting rule.
Quick Recap
Preflight checklist before publishing
- Confirm the specific field being validated and its documented limit unit.
- Check the API version, account or plan scope, and—where relevant—the target Mastodon instance configuration.
- Apply documented special handling, such as Mastodon’s mention rule or X’s weighted counting configuration.
- Test representative input that includes joined emoji, combining characters, and URLs; do not assume all emoji sequences behave alike.
- Keep byte-offset calculations separate from length checks, especially when generating rich-text annotations.
- Treat a local count as advisory and the target API’s validation as authoritative.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
