Nostr Character Counter

The Nostr character counter is a free browser tool that measures the length of any note you plan to broadcast to Nostr relays, showing the character count, byte size, and word count in real time so you can fit the feel of the network without guessing. Nostr is different from Twitter, Bluesky, or Mastodon because the protocol itself does not enforce a single character limit, which makes a lightweight counter more useful than you might first expect. Clients, relays, and downstream zap services each apply their own soft limits, so a note that looks short in one app may be truncated, collapsed behind a “show more” link, or rejected entirely by a strict relay. This counter gives you one place to paste a draft, watch the numbers climb, and adjust before you sign the event with your private key.

Whether you are writing a quick kind 1 micro-note, drafting a long-form NIP-23 article, updating your profile bio, or sketching out a threaded reply chain, a dedicated Nostr note length tool keeps you aware of how each client will render the result. Postiz built this counter for creators who publish across Nostr and traditional social platforms at the same time and need a consistent way to judge note length before posting.

How Nostr handles character and note length

Nostr is a simple, relay-based protocol where each message is a signed JSON event. Because the specification focuses on event structure rather than content formatting, there is no universal cap on how long a note can be. That flexibility is part of what makes Nostr attractive, but it also means creators have to think about length in a more nuanced way than on centralized networks.

There is no protocol character limit

The core Nostr protocol, defined across the NIPs (Nostr Implementation Possibilities), does not set a maximum character count for the content field of an event. In theory you could publish a novel inside a single kind 1 note. In practice, relays and clients choose their own boundaries, so the effective limit depends entirely on where your note is being stored and who is reading it.

Client soft limits shape the reader experience

Most popular Nostr clients apply a soft visual limit. Damus, Amethyst, Primal, Iris, Snort, Coracle, and Nostur typically show the first 240 to 500 characters of a note before collapsing the rest behind a “read more” affordance. Some clients treat very long kind 1 notes as spammy and push them lower in feeds. If your goal is to be read in full on the timeline, keeping a kind 1 note under roughly 280 to 500 characters is a safe target, and this counter shows you the moment you cross those thresholds.

Kind 1 notes versus NIP-23 long form articles

Nostr events have a kind number that tells clients how to render them. A kind 1 note is the classic micro-post: short, conversational, feed-friendly. A NIP-23 long form article uses kind 30023, supports markdown, includes a title and summary, and is treated like a blog post rather than a status update. If you find yourself writing past a thousand characters for a general audience, moving to NIP-23 often produces a better reading experience and more durable content. Use the counter to decide which lane suits the draft you are working on.

Relay byte limits and payload size

Relays do not think in characters, they think in bytes. Each relay operator can set a maximum event size, commonly between 16 KB and 256 KB per event, to protect storage and bandwidth. Emoji, CJK characters, and accented letters use more than one byte in UTF-8, so a note that looks short can still be heavier than a longer ASCII note. The counter surfaces both the character count and the UTF-8 byte count so you can stay under the byte ceiling of the relays you broadcast to.

How to use the Nostr character counter

The tool is designed to give you an answer in a single glance. Everything happens in the browser, no account, no key, no pasted text leaving the page.

• Paste or type your draft into the text box at the top of the page.
• Watch the live counters for characters, UTF-8 bytes, words, and lines as you edit.
• Check the soft limit indicators for the 280, 500, and 1000 character benchmarks common in Nostr clients.
• Copy the cleaned text and paste it into Damus, Amethyst, Primal, or your Nostr scheduler when you are happy with the length.
• Reset and try another draft when you want to compare a short zap-friendly version against a longer one.

No text is sent to any server, so private drafts stay private. You can use the tool repeatedly across sessions without signing up.

Use cases for a Nostr character counter

Nostr creators run a wider range of content shapes than most other networks, so a good counter earns its place for several very different workflows.

Zap friendly micro notes

Zaps are Lightning payments attached to notes. Short, punchy kind 1 notes tend to attract more zaps because they read cleanly in the feed and do not force a tap-to-expand. A counter that flags the 280 and 500 character lines helps you sculpt bite-sized observations, hot takes, and one-liners that stay fully visible in every major client.

Long form NIP-23 essays

When you are drafting a NIP-23 kind 30023 article, you usually care about total word count, section length, and reading time. The counter gives you word and line totals so you can pace a piece like a regular blog post, and the byte readout keeps you mindful of relay limits even on very long drafts.

Profile bios and metadata

Nostr profile metadata lives in kind 0 events. Clients render the “about” field very differently, and many truncate bios aggressively. Using the counter to keep a bio under around 160 characters usually produces the cleanest rendering across Damus, Amethyst, Primal, and the web clients.

Threads and reply chains

When a single idea will not fit a short note, many Nostr users build a thread of kind 1 replies. The counter helps you break a draft into evenly sized parts, each of which reads well on its own while still chaining cleanly together. Planning the split before you post avoids awkward mid-sentence breaks.

Cross posting to other networks

Many creators repost Nostr content to X, Bluesky, Mastodon, Threads, or LinkedIn. Checking the character count before you publish tells you whether the same text will survive the 280 character limit on X, the 300 character limit on Bluesky, or the 500 character limit on Mastodon without edits. Postiz scheduling customers often draft once in this counter and push the same text to every connected network.

Best practices for writing Nostr notes

Once you have a counter in hand, a few habits make your notes easier to read and more likely to spread across the Nostr network.

• Front load the hook so the first 240 characters can stand on their own, since that is what most clients show before truncation.
• Match the event kind to the length, using kind 1 for short notes and NIP-23 kind 30023 for anything past a few paragraphs.
• Mind the byte count, not just the character count, especially when your note contains emoji, CJK text, or math symbols.
• Avoid wall-of-text formatting by breaking long kind 1 notes into short paragraphs with blank lines between them.
• Use hashtags sparingly since Nostr clients index them but readers still count every character.
• Write a self-contained reply so people who arrive from search or a quoted note can understand the point without loading the full thread.
• Keep links short or rely on a client that fetches previews, since raw URLs count against the visible length.

Frequently asked questions

Does Nostr have a character limit?

The Nostr protocol itself does not set a character limit. Individual clients and relays enforce their own soft limits, usually between 280 and a few thousand characters for kind 1 notes, plus a byte ceiling per event for relays. This counter helps you stay on the right side of those practical limits.

What is the ideal length for a Nostr note?

For a kind 1 micro-note that stays fully visible in the feed, aim for under about 280 characters. Up to roughly 500 characters is still comfortable in most clients. Anything longer reads better as a NIP-23 long form article with a title and summary.

Why does the byte count differ from the character count?

Nostr relays measure event size in bytes, and UTF-8 encodes many characters using more than one byte. Emoji typically use four bytes, CJK characters use three, and accented Latin letters use two. The counter shows both values so you can avoid surprises from relay size limits.

Is this tool safe for private drafts?

Yes. The counter runs entirely in your browser. Your text never leaves the page, so you can paste sensitive or unpublished drafts without worrying about a server storing them.

Can I use the counter for other networks too?

Yes. Because it reports raw characters, bytes, and words, it works well for Twitter and X, Bluesky, Mastodon, Threads, and LinkedIn drafts. Many creators use it as a universal counter before cross posting the same idea across every network they run.

Does the counter support markdown for NIP-23 articles?

The counter measures your text as written, including markdown syntax characters. For NIP-23 drafts you can treat the character and word totals as a close estimate of the final rendered length, since markdown symbols take up only a small share of a long article.

Schedule and repurpose Nostr content with Postiz

Postiz is an open source social media scheduler built for creators who publish across Nostr, X, Bluesky, Mastodon, Threads, LinkedIn, YouTube, TikTok, Instagram, and more from a single calendar. You can draft a note here, check it with the Nostr character counter, then hand it off to Postiz to queue, cross post, and track performance without juggling separate apps for each network. Try it free at Postiz and keep every Nostr note the right length from the first draft.