Technical Architecture

Why This Site Doesn't Communicate

"Is my input data really not being sent to any external server?" — As a developer, that concern is completely natural. Rather than asking for blind trust, we provide a Zero-Network, local-first architecture that you can 100% verify yourself using DevTools.

1

1. Design Philosophy: Zero-Network Architecture

All 58+ web tools provided on this site (Base64, JSON formatter, JWT decoder, hash calculator, image compressor, CSS generators, etc.) never transmit your input data to any external server. All execution happens entirely inside your browser's JavaScript/Wasm engine.

API keys, encrypted passwords, confidential JSON, private images — nothing ever leaves your device over the network. Open your browser's DevTools Network tab, and you can confirm in real time that zero outgoing requests are triggered.

Works seamlessly in airplane mode, weak signal areas, or restricted corporate intranet environments once loaded.

2

2. PWA & Service Worker Asset Caching

The site is engineered as a Progressive Web App (PWA). A Service Worker automatically caches static assets (HTML, CSS, JS) into the Cache Storage API.

Previously visited tool pages load instantaneously from local cache even when offline. Reloading or revisiting pages produces zero network overhead.

Inspect registered workers and cached assets under DevTools → Application → Service Workers / Cache Storage.

3

3. Strict Content Security Policy (CSP) Enforcement

We enforce a strict Content Security Policy (connect-src 'self') via HTTP headers and meta tags. This mechanically blocks outgoing requests (fetch, XMLHttpRequest, WebSocket, EventSource) to external domains at the browser engine level.

Even if a third-party script or browser extension attempts malicious behavior, the browser's security layer forcefully intercepts and prevents external transmission.

4

4. Web Crypto API & Native Browser Standards

Hash calculations (SHA-256, SHA-384, SHA-512, etc.) and key verifications leverage the standard Web Crypto API (window.crypto.subtle). No external server computation is required.

Base64 encoding/decoding, JSON parsing, regex matching, and UUID v4 generation run completely inside client-side JS memory.

5

5. Strict Isolation Between Analytics & Tool Inputs

We use Google Analytics solely for overall site traffic and usability improvements (pageviews, session durations).

Tool inputs (raw text, JSON, images, generated code) are strictly isolated from analytics event objects and cannot leak into tracking pipelines.

6

6. In-Memory Image & Media Processing (Canvas / OffscreenCanvas)

Image compression, resizing, WebP/AVIF conversion, and color picking utilize the Canvas API and OffscreenCanvas directly on your device GPU/memory.

Images are never uploaded to any server. Converted outputs (Blob / Data URL) are generated in-memory and made available for immediate download.

7

7. How to Verify Yourself (DevTools)

Press F12 to open Developer Tools and select the Network tab.

Check 'Preserve log' and interact with any tool (input text, convert, copy, download). Observe that zero new network requests are generated.

Toggle Airplane Mode or disconnect Wi-Fi — every tool continues to work without interruption.

Last updated: July 2026