What is the difference between npub and note?

npub encodes a 32-byte public key; note encodes a 32-byte event ID. They use the same bech32 alphabet, so the prefix is what tells clients how to interpret the value.

Why do nevent and naddr contain more than an ID?

They embed relay hints, an author or a kind so a client can find the referenced event or address without extra requests. Decoding shows those extra fields separately.

Can I decode an nsec here?

Yes, but only in your browser: the page never transmits the value. Treat any decoded nsec as a live private key and store it in a password manager, not in a note or chat.

Techvoyage

NIP-19 Converter

Decode and encode Nostr NIP-19 identifiers — npub, note, nevent, nprofile and naddr — directly in your browser.

NIP-19 or hex value

Decoded locally with nostr-tools. The JSON API accepts public identifiers only, never nsec.

About this tool

NIP-19 defines the bech32 formats used across Nostr: npub for public keys, nsec for secret keys, note for event IDs, and nevent, nprofile and naddr for richer references with relays and metadata. This tool converts between those strings and the underlying hex values. Secret keys are decoded locally only; the JSON API rejects nsec.

FAQ

What is the difference between npub and note?: npub encodes a 32-byte public key; note encodes a 32-byte event ID. They use the same bech32 alphabet, so the prefix is what tells clients how to interpret the value.
Why do nevent and naddr contain more than an ID?: They embed relay hints, an author or a kind so a client can find the referenced event or address without extra requests. Decoding shows those extra fields separately.
Can I decode an nsec here?: Yes, but only in your browser: the page never transmits the value. Treat any decoded nsec as a live private key and store it in a password manager, not in a note or chat.