Hashtag limits and sensible counts, by platform
Hashtags are labels that group posts by topic. Channels treat them differently: some cap them, some ignore all of them once you pass a cap, and some use a single topic tag. This guide lists what each channel documents and the lower number our free caption check warns about.
The short version
- A cap is a ceiling, not a target. Our check warns well below it, because a long row of tags makes a caption harder to read.
- Passing a cap can cost you more than the extra tags: on YouTube, a video with too many hashtags has all of them ignored.
- Threads uses one topic tag per post, so extra tags add nothing there.
Hashtag rules by platform
| Platform | Documented cap | Count we warn above | Confidence |
|---|---|---|---|
| 30 | 5 | Stated by the platform | |
| No documented cap | 3 | Approximate | |
| X | No documented cap | 2 | Stated by the platform |
| No documented cap | 5 | Stated by the platform | |
| TikTok | No documented cap | 5 | Approximate |
| YouTube | 15 | 3 | Stated by the platform |
| 20 | 5 | Approximate | |
| Threads | 1 | 1 | Approximate |
| Bluesky | No documented cap | 3 | Stated by the platform |
The count we warn above is our own conservative setting for a quick check. It is advice about readability, not a rule set by the channel and not a promise about reach. Stated by the platform means the cap appeared in that platform's own documentation when we last read it.
Using the numbers
- Choose tags that describe the post. A tag that does not fit the content only adds noise.
- Put tags at the end of the caption, after the point of the post, so the visible first lines stay readable.
- Write each tag in a way a screen reader can say: capitalise each word in a long tag, like #SpringLaunchWeek.
- Keep a short list of tags per topic and reuse it, so every post on a topic is grouped the same way.
Sources and how to verify
This article cites no external pages directly. The caps come from the reference table used by the Branvoya tools, which records a review date and a confidence level instead of presenting them as permanent. For every channel, open its own help documentation and confirm the current rule.