How it works

Every PDF and image tool on JobNirdesh processes files inside your browser tab. Here is exactly what that means, and where its limits are.

The life of a file

  1. You select a file. The browser gives the page a reference to the file on your disk. Nothing is transferred anywhere.
  2. It is checked locally. The first bytes are inspected to confirm it really is a PDF, JPG, PNG or WebP file — the file name and extension are not trusted. Size and count limits are applied.
  3. It is processed on your device. PDF work runs in a Web Worker (a background thread) using the open-source pdf-lib library. Previews use Mozilla’s PDF.js. Images are decoded and re-encoded with the browser’s own canvas encoders, also in a Web Worker where supported.
  4. You download the result. The output is created in memory and offered as a download link that points to data inside your tab.
  5. Everything is released. Select Start over, switch tools, reload or close the tab, and the app drops its references to your files and results and revokes the download links. Each processing job runs in a fresh worker that is terminated afterwards.

What is never done

  • Files are not uploaded to our server or any third party.
  • Files are not written to local storage, IndexedDB, cookies or any other browser storage.
  • File names and contents are never sent to analytics or advertising services. The tool pages do not load any additional scripts of their own.
  • After a reload, previously selected files are not restored — you start with an empty workspace.

Honest limits of browser memory

JavaScript cannot securely wipe memory on command. When the app releases a file, the browser frees that memory at a time of its choosing. Closing the tab is the most reliable way to end everything. Downloaded files are saved by your browser to your device; the site cannot see or delete them.

Because your device does the work, very large documents can be slow or exceed the memory a browser tab may use, especially on phones. Current limits are 200 MB per PDF, 50 MB per image, 50 files and 500 MB per task, and 50 megapixels per image. If a task runs out of memory you will see an explanation rather than a crash.

Verifying it yourself

Open your browser’s developer tools, switch to the Network tab and run any tool. You will see the page’s own code and assets load (and, like the rest of JobNirdesh, advertising requests), but no request that sends your file. You can also disconnect from the internet after the tool has loaded — processing still works.

Features that would need a server

Faithful Word-to-PDF conversion, OCR and advanced PDF compression need engines that do not run well in a browser. They are listed as planned. If any of them is ever offered with server-side processing, the tool page will say so prominently before you select a file, and files would be deleted immediately after processing.