IAB TCF v2 Consent String Decoder
Reads an IAB TCF v2 consent string (the euconsent-v2 cookie) and lists every field it holds.
Use the tool
Why this tool exists
A TC string packs a visitor's consent choices into a short base64 text. It holds dates, the consent tool that made it, purposes with consent or legitimate interest, special features, vendor ids and publisher restrictions.
This decoder reads the bit layout from the IAB specification and checks it against a hand-built encoder, including range-encoded vendor lists and the extra segments. Vendor names are not shown because they need IAB's Global Vendor List, which is large and changes. The tool does not check whether a string is valid for a given vendor list.
How to use it
- Copy the euconsent-v2 cookie value from your browser, or the string from your CMP.
- Paste it into the box.
- Read the core segment, purposes and vendor lists.
- Look up vendor ids in the Global Vendor List if you need names.
Frequently asked questions
Does it support TCF v1?
No. Only v2 strings (version 2) are decoded.
Why are vendor names missing?
Names live in the Global Vendor List, which is not bundled. Only ids are shown.
Is my string sent anywhere?
No. It is decoded in your browser.