Urgent.News

What's breaking now, across thousands of outlets.

Tech

Social Media Character Limits: What 11 Networks Actually Count

Social media character limits look like the simplest fact in marketing: one number per network. Read the developer documentation behind those numbers and they stop being simple. Bluesky counts what you see, Threads counts some emoji as several characters, YouTube counts bytes, Mastodon counts every link as 23 and DEV leaves spaces out of its title count. We read each network's own documentation…

Social media character limits vary widely between platforms, ranging from a minimal 300 characters on Bluesky to an extensive 40,000 characters on Slack. These limits are not always straightforward, as different networks count characters differently and have unique rules.

Bluesky counts a character as a visible grapheme, with a maximum limit of 300 graphemes or 3,000 bytes. Threads counts emojis by their UTF-8 byte count, meaning a single emoji can consume multiple characters. YouTube counts bytes in descriptions, which can vary based on language. DEV leaves spaces out of its title character count.

Mastodon's default limit is 500 characters, but links count as 23 characters, while mentions count only the username. Instagram used to allow up to 30 hashtags, but has since limited posts to 5 since December 2025. Facebook does not publicly document a character limit.

When crafting content for social media, it's crucial to consider the specific counting rules of each platform. The same sentence can vary greatly in length across different networks. For example, a sentence with multiple emojis may take up more characters on Threads than on Bluesky. Furthermore, Instagram has reduced its hashtag allowance, making it essential to plan content accordingly.

In summary, the character limits for various social media platforms range from 300 to 40,000 characters. These limits differ in how characters are counted and include additional rules such as counting emojis by byte count, excluding spaces from title counts, and limiting hashtags. Understanding these differences is vital for crafting effective content across multiple social media platforms.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why your Bolt.new or Cursor app works for you and breaks for everyone else

There is a moment in every Bolt.new or Cursor build where the app stops being a demo. Up to that point it is fun. You describe a screen, the thing appears, you describe a behaviour, the thing does it.

  • Lack of database causes data issues; seed data fails with more items.
  • No error handling leads to spinning spinners and blank screens.
  • Deployment issues due to local environment variables and databases.

How to Track WhatsApp Enquiries in Your CRM After a Website Click

Track a WhatsApp button click as website intent, an inbound message as a conversation, and sales qualification as a CRM outcome. Keep the three counts separate.

  • Clicking WhatsApp button triggers website action
  • First valid inbound message starts conversation
  • Track distinct events: click, conversation start, qualification

A job board that agents pay for: four x402 bugs we hit before a directory would list it

We run a small job board for AI agents at agent-job-board.obtranzat.workers.dev . No accounts, no API keys: an agent pays 0.02 USDC to read the board, 0.50 to post a job, 0.01 for an aggregated feed…

  • Agents pay 0.02 USDC to read job board, 0.50 USDC to post job
  • x402 v2 rail on Base (eip155:8453) facilitates payment process
  • Multiple fixes addressed HEAD request oversight, discovery, multi-rail handling, error handling

Why We Switched From Homegrown Feature Flags to LaunchDarkly (And What We Learned)

We built our own feature flag system three years ago. It started as a simple Redis hash: feature:new-checkout -> {enabled: true, percentage: 50} . A Rake task to flip it.

  • Switched from homegrown to LaunchDarkly after three years
  • Homegrown system lacked audit trail, segmentation, kill switch
  • Migration took two sprints, impacted day-to-day operations positively

More from Tuesday 17 November →