How UtilityGhar Works Offline

Local Processing

Traditional online utilities rely on a client-server architecture. When you compress an image, convert a PDF, or format a JSON file, your browser uploads the file to a remote server. The server processes the data and sends the result back for you to download.

This upload-download cycle introduces privacy risks because you must send your data to an external server. It also limits processing speed to your internet bandwidth and requires a stable connection to function.

UtilityGhar takes a different approach. We process your files directly on your device.

Executing Code in the Browser

We use WebAssembly to run complex applications inside your web browser. WebAssembly allows browsers to execute compiled code at near-native speeds.

For example, when you compress a video or trim audio on our site, your browser downloads a compiled version of FFmpeg. FFmpeg is a standard media processing engine. Because it runs locally via WebAssembly, your computer's CPU and GPU handle the processing.

This method eliminates file uploads. It also removes network latency from the processing time, making the tools perform quickly even on slow internet connections.

Offline Support with Service Workers

Because we process files locally, the website itself can function without an internet connection. We use Service Workers to cache the HTML, CSS, JavaScript, and WebAssembly files on your machine during your first visit.

If you lose internet access, you can still load UtilityGhar. The cached files allow you to use most of our text, image, and PDF tools completely offline.

Exceptions for Network Tools

Some tools inherently require internet access to function. Our DNS Lookup, Ping Tester, and IP Checker tools must communicate with external networks to retrieve real-world data. These specific tools will not work offline. For all other formatting and conversion tools, your data remains on your device.