Checklist

TCF v2.4 TC String Decoder and CMP Checker

Run the free scan

Free TCF v2.4 CMP checker. Decode a TC String in your browser, read its policy and vendor list versions, and check it before October 23. Not legal advice.

Decode a TC String

The string stays in this browser. Decode runs locally and does not send it anywhere.

In brief

Paste a TCF v2.x TC String on this page, including TCF v2.4 strings. The decoder runs in your browser, reads the policy and vendor list versions, and lists the purposes, vendors, and CMP fields the string encodes. That list is the CMP claim. Fresh and Reject still show which cookies, storage, and network hosts loaded. ConsentProbe can store those packs. A free US-baseline scan is not an EU or California legal conclusion. This page does not install a TCF SDK or a CMP, and it is not legal advice.

This FAQ explains how to read a TCF v2 TC String next to Fresh and Reject runtime: cookies, storage, and Network. It is not legal advice, does not install a TCF SDK or a CMP, and is not a GDPR, ePrivacy, CPRA, or other compliance certificate. ConsentProbe reports are technical observations of what fired. They do not say what counsel would allow. Observation is not counsel permission.

Last updated October 16, 2026. This page owns string versus runtime. The CMP claims page owns banner text. The Consent Mode page owns those signals. The Reject leftovers guide owns a Reject failure. The evidence pack owns the handoff. This FAQ stays on the decoder. It does not paste those pages.

Short answer

This page decodes an IAB TCF v2 TC String in the browser, including strings from TCF v2.4 CMPs. The result lists the version, CMP fields, purpose consents, purpose legitimate interests, special feature opt-ins, and vendor id lists the CMP encoded. That decode is the claim. It does not prove marketing cookies, storage, or network hosts stayed off.

After you decode, or screenshot the CMP purpose UI, still run Fresh and Reject. Write one finding sentence when the decoded claim and the runtime disagree. The string-versus-runtime frame is on this page. Open the CMP claims page, the Consent Mode page, the Reject leftovers guide, and the evidence pack for the other frames.

The attestation FAQ is optional reading. The decoder does not install a TCF SDK. ConsentProbe does not install a CMP and does not configure TCF. A free US-baseline scan is not an EU or California legal conclusion.

Decode and runtime

A decoder, a CMP dashboard, and a labeled browser visit answer different questions. Keep the finding as decode and runtime disagree. Leave permission with counsel. The longer falsification essay is on this page. This FAQ stays on the decoder question.

Swipe to see more

What a TCString decode shows, and what Fresh and Reject still have to record.
LayerWhat it isWhat it does not prove alone
TCString decode or decoder outputReadable purposes and vendors from the encoded stringThat cookies and network hosts stayed off
CMP dashboard or purpose UIAn operator-facing claim about the same stringThat the browser Network matched the UI
Fresh or Reject cookies and NetworkWhat the browser set and requested on a labeled visitLegal permission from counsel

Use the decoder at the top of this page, or the CMP purpose UI, to read purposes and vendors as claims. These steps do not teach TCString bit layout, vendor-list registration, or SDK install.

  1. Use a clean profile. Load the storefront once. Do not click Accept, or use the state under test, such as Reject or a claimed denial.
  2. Note that a TCString exists in DevTools or the CMP API. Decode it with the tool on this page, or read the purpose UI. Treat purposes and vendors as claims.
  3. Capture cookies, storage, and Network for ads, analytics, and marketing hosts. Label the pack Fresh, or Reject if that is the state you loaded.
  4. Write one finding sentence when the decode says limited or denied and Network looks like Accept.
  5. Keep the evidence pack for handoff. The deeper frame is on this page. Open the Reject leftovers guide when Reject is the failure.

What to check in a TC String before October 23, 2026

IAB Europe set October 23, 2026 as the deadline for web CMPs to implement the TCF v2.4 disclosures. CMPs in mobile apps and on CTV have until February 23, 2027. Most v2.4 changes are banner text, so a decode covers only part of the check.

  1. Read TCF policy version in the decoder. The current Global Vendor List (version 181, October 15, 2026) declares policy version 5. TCF v2.4 kept that number. Policy version 5 has been in the vendor list since July 2024, after TCF Policies 5.0 added Special Purpose 3. A string at policy version 4 or lower was made under older policies, and the IAB Tech Lab specification says the CMP has to ask the user again when the numbers differ.
  2. Read Vendor list version. IAB Europe published the v2.4 vendor list on July 23, 2026. Version 169 is the first list with the standard Features text and the new Special Feature 2 name. A string built from version 168 or lower came before those texts. CookieHub says stored strings stay valid and are rewritten the next time the visitor saves a choice, so a returning visitor can still carry an older number.
  3. Check the Special Feature 2 name on the banner. IAB Europe renamed it from "Actively scan device characteristics for identification" to "Identify devices based on information actively requested". The string still stores it as opt-in 2 under Special feature opt-ins, so the decode looks the same before and after the rename. Open the banner's second layer and read the name there.
  4. Check Purposes 3 and 4 if the site uses CookieHub. Stack 10, "Personalised advertising", groups Purpose 3 (Create profiles for personalised advertising) and Purpose 4 (Use profiles to select personalised advertising). The v2.4 vendor list left Stack 10 as it was. CookieHub 2.9.3 added Stack 10 to its default TCF setup and limited "Accept all" to what the dialog presents. Accept all on the site, decode the string, and look for 3 and 4 under Purpose consents. Then clear the site data, click Reject All, decode again, and compare.
  5. Check the CMP release. CookieHub shipped TCF v2.4 support in widget 2.9.3 on September 23, 2026. Usercentrics tells Web SDK customers to update to version 4.64.0 before October 23, 2026. The CMP version field in the string is a number the CMP assigns, and it does not spell out a release like 2.9.3 or 4.64.0. Confirm the release in the CMP dashboard or with the CMP's support. In IAB Europe's CMP list, CookieHub is CMP ID 354 and Usercentrics is CMP ID 5.

Swipe to see more

What a TC String decode shows for each TCF v2.4 check
CheckVisible in the decodeWhere else to look
Policy versionYes, TCF policy versionCurrent Global Vendor List
Vendor list versionYes, Vendor list versionVersion 169 or higher carries the v2.4 texts
Special Feature 2 nameNo, only opt-in 2Banner second layer
Purposes 3 and 4Yes, Purpose consentsBanner: is Stack 10 shown?
CMP releaseNo, only a CMP version numberCMP dashboard or support

When the decoded claim and Network disagree

Example, not a customer capture: a decoder lists a marketing purpose as not allowed, and Fresh Network still requests an ads host before any banner click. Save the request URL and a screenshot of the purpose UI.

A denied purpose does not cancel a request the tag already sent. This page covers that split. A Consent Mode denial is a separate claim on the Consent Mode page.

The decoder on this page reads the claim. ConsentProbe records Fresh and Reject so you can compare runtime with that decode. Hand-matching those claims across templates takes a long time.

FAQ

What is a TCF consent string decoder?

This page decodes a v2 TC String in the browser into purposes, vendors, and CMP fields. Use that as the CMP claim, then check cookies and Network on Fresh and Reject.

How do you decode a TCF consent string for a cookie audit?

Paste the string into the decoder on this page. Read the purpose and vendor ids, then capture Fresh and Reject cookies and Network and compare them with that claim.

Does decoding a TCString prove cookies stopped?

No. The decode is the claim layer. Fresh and Reject are the evidence layer. This page holds the longer comparison.

Is this a TCF SDK or CMP install guide?

No. The decoder reads a string you already have. It does not register a vendor, install a TCF SDK, or walk a purpose bitfield.

Which TcfPolicyVersion is TCF v2.4?

Policy version 5. TCF v2.4 kept the number that TCF Policies 5.0 introduced in 2024, so the decoder also reads the vendor list version. A string built from Global Vendor List 169 or higher used the v2.4 texts.

Is this a CMP checker?

It checks what a CMP wrote into the TC String, including the policy version, vendor list version, purposes, and vendors. IAB Europe's CMP Validator extension tests the CMP's API on a live page. Neither tool shows which requests loaded after Reject All.

Does ConsentProbe include a TCF decoder?

This page decodes a TC String in the browser. The audit records Fresh and Reject evidence packs tied to requests, cookies, and screenshots. The audit report does not decode the string.

Is this legal advice?

No. These are technical observations. It is not legal advice. Observation is not counsel permission. ConsentProbe does not replace counsel, and it does not install a CMP.

Limits of this page

This page decodes a TCF v2 TC String in the browser. Fresh and Reject still show what the browser did. It does not install a TCF SDK. It is not legal advice. Observation is not counsel permission. A free US-baseline scan is not an EU or California legal conclusion.

String versus runtime is on this page. Open the CMP claims page for banner text, the Consent Mode page for those signals, the Reject leftovers guide when Reject still tracks, and the evidence pack for the handoff. The attestation FAQ is the optional sibling for vendor badges.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

Check what loads after Reject All

The decode shows what the CMP wrote. It does not show what loads after the click. The Reject All tracking page lists the ways to check that.

Save a US-baseline technical record

After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.

TCF v2.4 TC String Decoder and CMP Checker | ConsentProbe