For developers

Chromium DevTools, none of the Chrome

Q: Does Dazr have a JSON viewer?

Yes, built in. Open a .json file or hit a JSON endpoint and you get a tree-view inspector with collapsible nodes, search, and copy-as-path. There's a built-in PDF viewer too, and a UBL invoice viewer (a B2B XML format that the rest of the browser world ignores).

Q: Will localhost / 127.0.0.1 work for development?

Yes. Dazr's private-network protection prevents public sites from making requests to your localhost (which is good, it stops a malicious site from probing your dev server). You opening localhost yourself works normally. Self-signed HTTPS certs prompt the same way they do in Chrome.

Same engine, same DevTools, same extensions you already know. Without the Google account, the telemetry, the Manifest V3 lobotomy of your blocker, or the 4 background requests per minute to *.google.com. Dazr is the European Chromium build for developers who don't want their browser to also be an analytics product.

Download Dazr Privacy details

What you get out of the box

Everything a developer expects, none of the data harvesting.

Chromium DevTools, unmodified

Elements, Network, Console, Sources, Performance, Application, all the panels you already know, with the same shortcuts. F12 opens them. $0, $_, copy(), all the console helpers work the same way.

Built-in JSON viewer

Open a .json file or hit a JSON endpoint and get a real tree view with collapse, search, and copy-as-path, not a wall of unformatted text. There's a PDF viewer and a UBL viewer built in too.

localhost actually works the right way

You can open localhost:3000, 127.0.0.1, or any IP address. Self-signed HTTPS certs prompt the same way. The private-network protection only blocks public sites from making requests to your localhost, which is what you want.

Per-site privacy overrides

Need to disable the ad blocker on a site you're testing? One click. Need to drop anti-fingerprinting to standard or off for a specific site? Per-site override. Privacy defaults stay sensible everywhere else.

Vertical tabs (when 30+ tabs is normal)

Toggle vertical tabs in settings. With horizontal tabs, anything past tab #15 is a single-pixel slice you can't read. Vertical scales linearly with tab count.

Open-source friendly

The fingerprint-defense extension is being open-sourced separately. The browser uses Chromium (open), the Ghostery adblock engine (open), and standard libraries you can audit.

For the work you do every day

The browser doesn't pollute your network captures

Open Wireshark or any HTTP proxy and watch a Chrome session, you'll see dozens of background requests to *.google.com: telemetry, search suggestions, "experiments", safe-browsing checks, sync. When you're trying to debug your own app's traffic, that noise is real. Dazr originates exactly two background connections: an update check every 4 hours, and DNS lookups. That's it.

No *.google.com in your captures
No chrome:// sync chatter
One predictable update check per 4 hours

A real ad blocker, not the Manifest V3 version

Chrome's Manifest V3 capped what content blockers can do. The full version of uBlock Origin no longer works in Chrome. If you spend any time browsing news sites or technical forums while researching, the difference is huge. Dazr ships its own full-strength blocker built into the browser, with the same blocklists uBlock Origin uses.

EasyList + EasyPrivacy + uBlock quick-fix lists, refreshed weekly
Ghostery's open-source adblock engine
One-click toggle per site

EU servers, not US cloud

The browser's update server, search backend, and DNS resolver are all European. No AWS, no GCP, no Azure under the hood. For developers who care about EU sovereignty, or who work for organisations that do, the data path is clean by default.

EU-hosted update server
EU-hosted search backend (no Google or Bing upstream)
European non-profit DNS
Open-source, auditable infrastructure stack

Frequently asked questions

Are the DevTools the same as Chrome's?

Yes. Dazr is Chromium-based, so the DevTools are the same Chromium DevTools you already know, the Elements panel, Network panel, Console, Sources debugger, Performance profiler, Application storage inspector. F12 or Ctrl/Cmd+Shift+I opens them. Bookmarks for the dev-tools panels even work the same way.

Will my Chromium extensions work?

Yes. Dazr supports loading Chromium extensions, React DevTools, Vue DevTools, Redux DevTools, Wappalyzer, JSON Viewer, ColorZilla, Postman, the lot. Install them as unpacked extensions; the Chrome Web Store itself isn't integrated (that's a Google account hook), but the extensions themselves work the same way.

Does Dazr have a JSON viewer?

Yes, built in. Open a .json file or hit a JSON endpoint and you get a tree-view inspector with collapsible nodes, search, and copy-as-path. There's a built-in PDF viewer too, and a UBL invoice viewer (a B2B XML format that the rest of the browser world ignores).

Will localhost / 127.0.0.1 work for development?

Yes. Dazr's private-network protection prevents public sites from making requests to your localhost (which is good, it stops a malicious site from probing your dev server). You opening localhost yourself works normally. Self-signed HTTPS certs prompt the same way they do in Chrome.

Can I disable anti-fingerprinting on a single site for testing?

Yes. Per-site overrides let you drop anti-fingerprinting to standard or off for a specific site (useful for testing fingerprinting code, or for legitimate sites that genuinely break with strict mode). Other privacy defaults stay on.

Is there a way to test what data the browser sends?

Yes, open Wireshark, Charles, or your favourite proxy and watch. Dazr originates exactly two background connections: an update check to dazr.eu every 4 hours, and DNS lookups to dns0.eu. Everything else is sites you visit.

Same engine. Cleaner network log.

Same Chromium, same DevTools, same extensions. Without the analytics business attached.

Download Dazr