URI Record
An NDEF record that encodes a URI (web URL, phone number, email, etc.) using compact prefix codes. The first byte indicates the URI scheme (0x04 = 'https://', 0x03 = 'http://', etc.), reducing storage requirements.
What Is an NDEF URI Record?
An NDEF URI recordURI recordNDEF record encodingencodingData writing to NFC tags during manufacturing productionView full → URIs with compact prefix compressionView full → (TNF 0x01, Well-Known Type "U") encodes a Uniform Resource Identifier — a web URL, telephone number, email address, or other URI-scheme resource. URI records are the most common NDEF type in deployed NFC tags. When a smartphone reads one, the OS automatically opens the URL, dials the number, or launches the appropriate handler without requiring a user-installed app.
URI Prefix Compression
The first payload byte is a URI Identifier Code representing a common prefix:
| Code | Prefix | Bytes Saved |
|---|---|---|
| 0x00 | (none) | 0 |
| 0x01 | http://www. | 11 |
| 0x02 | https://www. | 12 |
| 0x03 | http:// | 7 |
| 0x04 | https:// | 8 |
| 0x05 | tel: | 4 |
| 0x06 | mailto: | 7 |
The NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full → defines 36 prefix codes (0x01-0x23). Code 0x00 stores the full URI as-is.
Memory Example
Storing https://example.com/product/12345:
- Without compression: 37 bytes URI + 5 bytes overhead = 42 bytes
- With code 0x04: 1 byte code + 29 bytes remainder + 5 bytes overhead = 35 bytes
On NTAG 213 (144 bytes user memory), this 7-byte saving represents nearly 5% of total capacity.
Payload Format
[URI Identifier Code: 1 byte] [URI Field: variable]
The complete URI is reconstructed by concatenating the prefix from the code lookup with the URI field. Code 0x00 means the URI field contains the full URI including scheme.
Platform Behavior
Android: Creates an ACTION_VIEW intent with the URI. If an AAR follows in the same NDEF message, the intent targets the specified app.
iOS: Displays a notification on iPhones with background tag reading (XS+). Tapping opens the URL in Safari or the associated universal link app.
Best Practices
- Use HTTPS (code 0x04) — browsers flag HTTP as insecure; iOS may block non-HTTPS.
- Shorten URLs for long addresses to conserve user memory.
- Combine with Smart Poster for marketing tags needing human-readable titles.
- Use SDM-enabled chips for authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full → tags with dynamic URL parameters.
Related Terms
Related Guides
คำถามที่พบบ่อย
The NFC glossary is a comprehensive reference of technical terms, acronyms, and concepts used in Near Field Communication technology. It is designed for developers, product managers, and engineers who work with NFC and need clear definitions of terms like NDEF, APDU, anti-collision, and ISO 14443.
Each glossary term is cross-referenced with related NFC chips, standards, and other terms. For example, the term 'AES-128' links to chips that support AES encryption (NTAG 424 DNA, DESFire EV2/EV3), and the term 'ISO 14443' links to all chips compliant with that standard.
Yes. NFCFYI provides glossary definitions in 15 languages including English, Korean, Japanese, Chinese, Spanish, Portuguese, Hindi, Arabic, French, Russian, German, Turkish, Vietnamese, Indonesian, and Thai. Use the language selector in the header to switch languages.