NDEF

NDEF (NFC Data Exchange Format)

<\/script>\n
'; }, get iframeSnippet() { const domain = '{ SITE_DOMAIN }'; const type = '{ embed_type }'; const slug = '{ embed_slug }'; return ''; }, get activeSnippet() { return this.method === 'script' ? this.scriptSnippet : this.iframeSnippet; }, copySnippet() { navigator.clipboard.writeText(this.activeSnippet).then(() => { this.copied = true; setTimeout(() => { this.copied = false; }, 2000); }); } }" @keydown.escape.window="open = false" @click.outside="open = false">

Embed This Widget

Theme


      
    

Widget powered by . Free, no account required.

The standardized data format defined by the NFC Forum for storing and exchanging data on NFC tags. NDEF messages contain one or more records, each with a type, ID, and payload. It's the universal format understood by all NFC-enabled smartphones.

별칭: NDEF NFC Data Exchange Format

What Is NDEF?

NDEF (NFC Data Exchange Format) is the standardized data format defined by the NFC Forum for organizing, storing, and exchanging information on NFC tags and between NFC devices. NDEF provides a universal container format understood by all NFC-enabled smartphones regardless of manufacturer or operating system.

NDEF Architecture

NFC Tag Memory
  +-- Capability Container (CC)
  +-- TLV Wrapper
       +-- NDEF Message
            +-- NDEF Record 1 (e.g., URI)
            +-- NDEF Record 2 (e.g., Text)
            +-- NDEF Record N (e.g., AAR)

An NDEF message contains one or more NDEF records. Each record carries data with type identification. The message is wrapped in TLV encoding and preceded by a capability container.

Common NDEF Record Types

Record Type TNF Type Use Case
URI 0x01 "U" Web URLs, phone numbers
Text 0x01 "T" Human-readable text
Smart Poster 0x01 "Sp" URI + title + metadata
MIME 0x02 type vCards, Wi-Fi credentials
External 0x04 domain:type Custom app data
AAR 0x04 android.com:pkg Force Android app launch

Why NDEF Matters

Before NDEF, contactless applications required custom software with proprietary formats. NDEF solved this by establishing a format that works everywhere (any NFC phone, no app required), is self-describing (records carry type metadata), composable (multiple records per message), and compact (URI prefix compression minimizes memory usage).

NDEF Formatting

Tags must be "NDEF formatted" before storing messages. Formatting writes the capability container and initializes the TLV structure. Most NTAG and MIFARE Ultralight chips ship pre-formatted. DESFire and ICODE chips require an initial formatting step.

Memory Usage

A simple URL like https://example.com requires ~15-20 bytes (including TLV overhead and URI prefix encoding). Complex payloads like vCards may require 200-500 bytes. Ensure your payload fits within the chosen chip's user memory.

Related Terms

자주 묻는 질문

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.