Do Not Track Checker — DNT & GPC Status
Generate a JavaScript snippet to check if Do Not Track (DNT) and Global Privacy Control (GPC) are enabled.
How it works
- 1Configure your options above
- 2Click "Generate" — processing happens in your browser
- 3Copy or download the result
What to do next
About Do Not Track Checker
Do Not Track Checker is a single-page tool for the common web and productivity utility task it is named after. Generate a JavaScript snippet to check if Do Not Track (DNT) and Global Privacy Control (GPC) are enabled. The interface keeps the input on one side, the configurable options in the middle, and the result on the other side. Most jobs start and finish without any scrolling.
Under the hood, Do Not Track Checker uses standard browser APIs to do the actual work. Input runs through the same engine, with a per-file ceiling of 0 MB so memory usage stays predictable on lower-end laptops and tablets. The engine ships as part of the page bundle, so once the page is loaded the tool keeps working even if your network connection drops.
Do Not Track Checker is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.
The architecture is local-first by design. Once the page is loaded, you can disconnect from the network and the tool still completes the job. The processing stack — standard browser APIs and the small UI shell wrapping it — ships with the page itself, so the tool keeps working in offline conditions, on a captive-portal Wi-Fi, or behind a corporate proxy that limits what the tab can reach.
The hard constraints are easy to remember. Maximum input: 0 MB. Multiple files per run: no — one input at a time, by design, to keep results predictable. The same controls apply on every run.
Do Not Track Checker is intentionally narrow in what it does, which makes it easy to slot into a longer workflow. Take its output, hand it to whichever next tool fits the job, and Do Not Track Checker stays out of your way until the next time you need it.
Common audiences for Do Not Track Checker include creators experimenting with formats and site owners auditing pages, but plenty of people land on the page through a one-off search and never come back — that is also fine. The tool is built to be useful even when you only ever need it once.
Once the engine finishes, the output is offered as an immediate download. There is no preview gate, no email-wall, and no "register to download" intermediary — the file is yours the moment it is ready.
Do Not Track Checker is honest about scope: it handles a single, well-defined web and productivity utility step. Specialist edge-case work — uncommon formats, very large inputs, or pipelines that need scripting — is what dedicated desktop apps are for. This page handles the common case quickly.
Do Not Track Checker is one example of a broader pattern: utility software increasingly works as single-page, client-side experiences. Every page in the catalog is shaped that way, which keeps each tool fast to load and easy to recommend in a single link.
Pro tip: Do Not Track Checker works just as well in a private/incognito window as in a normal one, which is occasionally useful when you want zero browser-history footprint of the job. Another tip: if the tool ever feels slow, it is almost always because the browser tab is competing for CPU with another tab — pausing or closing the heavy ones gives the engine room to work.
Do Not Track Checker fits the gap where opening a desktop app feels heavy and writing a script feels overkill. The page handles the common web and productivity utility task with sensible defaults so a single visit usually completes the job; for highly specialised work, a dedicated desktop application can offer more knobs to turn.
If Do Not Track Checker appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 0 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
That is the whole tool. Use Do Not Track Checker for as long as it stays useful to you, and if it does, the catalog has many more tools built the same way. Each applies the same single-purpose discipline, so the way you used this page transfers to the next one you try.
How it works
- 1Land on the Do Not Track Checker page. The tool is ready to use the moment the page renders.
- 2Add your web utility input by dropping it onto the page or browsing for it.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Trigger processing. standard browser APIs reads your input, applies the transformation, and writes the result back into the page.
- 5Download the result. The file is generated in your browser and saved through your normal download flow.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Run a fast accessibility check before publishing using Do Not Track Checker.
- Preview how a result looks before deploying it.
- Plan content without paying for a SaaS dashboard.
- Run a one-off check during a meeting without context-switching.
- Validate a setting before circulating it to a team.
- Compare two product variations side by side.
- Create a placeholder image for a wireframe.
- Pull a quick reference number for a status update.
FAQ
What is Do Not Track?
DNT is a browser signal requesting websites not to track you. Compliance is voluntary.
Is DNT effective?
Most websites ignore DNT. It was deprecated by the W3C. GPC has stronger legal backing in some jurisdictions.
What is GPC?
Global Privacy Control is a newer signal with legal weight under CCPA and GDPR.
How do I enable DNT?
Check your browser privacy settings — most browsers have a Do Not Track toggle.
What values does DNT return?
"1" means enabled, "0" means explicitly disabled, null/undefined means not set.
Private?
Yes — the snippet runs locally in your browser console.
Why use Do Not Track Checker instead of a paid online tool?
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. Do Not Track Checker sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common web and productivity utility operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.
How accessible is the Do Not Track Checker interface?
Do Not Track Checker uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.
Can I call Do Not Track Checker from a script?
Do Not Track Checker is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (standard browser APIs) is open-source and can be used directly from your own code.
Are jobs run with Do Not Track Checker stored anywhere?
Favtoo keeps no copy of your file because Favtoo never receives your file. Do Not Track Checker runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
What should I do if Do Not Track Checker fails on my file?
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is in a supported format and that it is below 0 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
How many times per day can I use Do Not Track Checker?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Do Not Track Checker as often as you need; every run produces a full-quality result.
How do I run Do Not Track Checker over a folder of files?
Do Not Track Checker processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
Is there a desktop version of Do Not Track Checker?
No installation is needed. Do Not Track Checker runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Do Not Track Checker on any computer you have temporary access to without leaving anything installed on it.