Decode IAB TCF Strings Instantly
The fastest way for AdTech professionals to inspect and validate Transparency and Consent Framework strings. Gain full visibility into consent signals with zero friction.
What is IAB TCF?
The Transparency and Consent Framework (TCF) helps parties in the digital advertising chain ensure they comply with the GDPR and ePrivacy Directive. These strings are often complex, base64-encoded bitfields that contain vital privacy choices.
Three Simple Steps
Validate any TC string in under 5 seconds.
Paste String
Copy your encoded TC string into our secure input field.
Decode
Our engine parses the bit-field data against the latest GVL.
Review Details
Get a full breakdown of purposes, vendors, and special features.
Engineered for Technical Auditing
Our tool isn't just a parser; it's a comprehensive audit suite for GDPR compliance. We provide the granular data points needed to verify every vendor's signal.
- check_circle Real-time Global Vendor List (GVL) sync
- check_circle Support for all TCF versions (1.0 to 2.2)
- check_circle Zero data logging for strict privacy
100%
Accuracy on bit-level parsing
<10ms
Instant decode performance
800+
Vendors tracked in GVL
Secure
Local-only processing
Powerful Features
Everything you need to inspect consent signals at scale.
Vendor List Support
Automatically fetches the latest Global Vendor List from IAB to map IDs to company names.
Purpose Breakdown
See exactly which of the 10 purposes and 2 special purposes have been consented to.
Versioning
Easily compare strings across different TCF versions to ensure backward compatibility.
Bit-Level Validation
Detect malformed strings or bits that don't align with the framework specification.
Mobile Responsive
Debug on the go. Our interface works perfectly on mobile browsers for quick field tests.
Export JSON
One-click export of the decoded data to JSON format for internal reporting and documentation.
Frequently Asked Questions
Is my consent string data stored?
No. All decoding is done client-side or in ephemeral memory. We do not store or track the contents of the strings you decode.
Does it support the Google AC String?
Yes, our tool can parse standard IAB TCF strings and identify additional vendors in the Google Additional Consent (AC) string extension.
What is the difference between TCF v2.0 and v2.2?
v2.2 introduces stricter requirements for legitimate interest and vendor disclosures. Our tool highlights these specific v2.2 fields automatically.
How often is the Vendor List updated?
We sync with the official IAB Global Vendor List every 12 hours to ensure you have the most up-to-date vendor information.
Ready to decode your first string?
Stop guessing what's inside your consent signals. Start validating your TCF implementation today.
