What Runs in the Browser During File Conversion

By PixelShift Security Labs • Updated May 2026 • 6 Min Read

Executive Summary

Some online converters upload the file, process it on a server, and send back a download. PixelShift's image, PDF, and upscale tools run in the browser. Your files aren't uploaded to a server. This article describes that behavior. It is not a certification.

1. The SaaS Paywall & The Server-Side Trap

Traditional file conversion utilities are designed as standard client-server applications. To perform a simple conversion, the user must upload their document to an external server. Once uploaded, the file is processed remotely, saved in storage, and then returned as a download link. While convenient, this model introduces major vulnerabilities for corporate operations:

  • Data Retention & Scrape Policies: Many free conversion platforms monetize by retaining user files, selling aggregated telemetry, or utilizing uploaded document text to train machine learning models.
  • Exposed Server Infrastructure: Files held in temporary server-side folders are targets for misconfigured cloud storage buckets, malicious insider actions, or direct cyberattacks on the conversion vendor.
  • A file leaves the device: Once a converter uploads the file, you no longer control where that copy is stored.

2. Anatomy of Client-Side Web Architecture

Browser technologies have evolved to the point where remote server-side processing is no longer required for file operations. By compiling high-performance native libraries to WebAssembly (Wasm) and leveraging modern HTML5 APIs, browsers can execute complex operations in local memory.

When a file is imported into PixelShift, the following sequence occurs within the client-side sandbox:

File Processing Flow Comparison

Upload-based converter
1. Drag file into browser
⬇ Upload via network (HTTPS)
2. Processed on Remote Server
⬇ File stored in DB/Temporary directory
3. Download back to local device
Result: Multi-party data exposure risk
PixelShift in the browser
1. Drag file into browser
⬇ Processed in Browser Sandbox
2. WebAssembly / Canvas Execution
⬇ File is not uploaded
3. Write directly to disk memory
Result: the file is not uploaded

The conversion code does not post the file. The page can still download its own scripts, and the first AI upscale downloads model weights from this site. If you accept analytics, Google Analytics receives page views and counts, not image bytes.

3. What else can leave the browser

File bytes stay on the device. A few other requests can still happen. They are not a certification of any regulation.

  • The site's scripts, the HEIC and AVIF libraries, and the ESRGAN model weights are downloaded from this site. Those requests do not include your file.
  • If you accept analytics, the page loads Google Analytics and sends page views plus counts: tool name, file count, format, mode, and download type.
  • Rejecting analytics leaves the conversion path unchanged. The file is still not uploaded.

4. Check whether a file is uploaded

You can check the network panel yourself. This does not mean every tool works with no network connection. The offline page cache stores scripts, CSS, HTML, and WASM. It does not store the AI upscale model files (.json and .bin), so the first upscale still downloads those from this site.

  1. Load the Web App: Open the conversion website in your browser.
  2. Disconnect the Internet: Switch your system into airplane mode or disable Wi-Fi.
  3. Perform the Conversion: Import a JPG, PNG, or WebP that the page can already decode and click convert. If that finishes with no upload of the file, the encode ran in the browser. AI upscale can still fail offline because its model weights are not in the page cache.
  4. Examine Network Activity: Open your DevTools (F12), navigate to the Network tab, and run a conversion online. Check for outgoing POST/PUT streams containing the file's bytes.

5. Image to PDF

The image to PDF tool builds the PDF in the browser with jsPDF. Your files aren't uploaded to a server. Each image the browser can decode is embedded as a JPEG at 85% quality, which is lossy.

Securing Your Corporate Workflows

The conversion tools run in the browser. Your files aren't uploaded to a server. Optional analytics is separate and starts only after you accept cookies.

Ready to integrate privacy-first tools into your organization's workflow? Try our range of processing features.

Keep learning

View all guides
PixelShift.cc

Secure Client-Side Converter...