NFC Tag Reader and Writer

Encode and decode NFC tag records, text, URLs, Wi-Fi credentials, vCards, and more, and write them from Android Chrome.

Compose

Fill in the fields above to see the record type, its NDEF bytes, and which common tags it fits on.

Read

Click Scan for tags, then hold an NFC tag to the back of the phone. Each reading is decoded with the same rules as the Compose and Decode sections above.

Write

Writes the record composed above to a tag. Hold the tag to the back of the phone when prompted.

Making a tag read only is permanent. Once set, no device, including this one, can ever write to that tag again.

Related tools

What it does

A pure NDEF encoder and decoder for NFC tags: text, URLs, Wi-Fi credentials, vCard contacts, geo coordinates, phone numbers, email addresses, SMS drafts, and Android app launch records. It builds the exact record bytes the NFC Forum's NDEF format defines, including the URL prefix abbreviation table and the Wi-Fi Simple Configuration TLVs that a phone's Wi-Fi settings screen understands, and it checks the result against the usable capacity of common tag chips: NTAG213, NTAG215, NTAG216, Mifare Ultralight and Topaz 512. Paste a hex dump from a scanned tag and it decodes the record back into readable fields the same way.

How to use it

Pick a record kind, type the value, and the tool shows the record type, a payload preview, the NDEF bytes as hex, the size, and which common tags it fits on. On an Android phone in Chrome, the write panel does the actual radio work: tap Scan to read a tag with the same decoder, or tap Write to send the composed message with NDEFReader, with a clearly labeled make read only option since locking a tag cannot be undone. On desktop or any other browser the page explains that Web NFC is Android Chrome only rather than pretending to work.

Why this one

Most NFC writer apps are phone only, ad supported, and give no way to see the exact bytes going onto the tag. This runs the same NDEF encoder in a page you already trust, shows the raw hex before you write anything, and warns about tag capacity before you find out the hard way that a long URL does not fit an NTAG213. Reading and writing use the phone's own Web NFC radio, so your files and inputs never leave your device: tag contents are read and written by your phone directly, and nothing about the tag or its contents is sent to this site.

FAQ
Which phones and browsers does this work on?
Web NFC, the browser API that talks to the phone's NFC radio, currently ships only in Chrome on Android. It is not available in Safari, Firefox, or any browser on iOS, and not in desktop Chrome either, since desktops rarely have an NFC reader. This page still works everywhere for building and decoding NDEF bytes by hand. The live scan and write panel checks for the API and shows an honest message instead of a broken button when it is missing.
Can I write a Wi-Fi tag that connects a phone automatically?
Yes. Choose the Wi-Fi credential kind, enter the network name, password, and security type as ssid;password;WPA2, and the tool builds a Wi-Fi Simple Configuration record: the same MIME record type and TLV layout Android and other phones read to offer one-tap connect when they tap the tag. WPA2 is the default security type; WPA, WEP, WPA/WPA2, and open networks are also supported.
Can this lock an NFC tag so it can never be changed again?
The write panel exposes NDEFReader's makeReadOnly option behind its own checkbox, separate from the write button, with a clear warning next to it. Making a tag read only is permanent: once set, no device, including this one, can ever write to that tag again. Leave the checkbox off unless you are certain the tag's final content is correct.

Keyboard shortcuts: press ? anywhere on this page to see them.