How DuckConvert Works
A plain explanation of the client-side architecture, plus a way to verify it yourself in under a minute. If you need to share this with an IT or security reviewer, you can print a clean summary below.
DuckConvert Technical Overview
Client-Side Architecture
1. How It Works
DuckConvert is a static site with no backend — there is no server that your files are ever sent to. All file parsing and conversion runs locally, in your browser, using WebAssembly (WASM) and Web Workers. Your files, images, documents, and spatial data stay on your own device throughout the entire process.
Runs On Your Device
Conversions run inside Web Workers on your own CPU. There's no queue, no upload progress bar, and no server-side step — the same browser tab that loaded this page does the actual work.
No Backend to Send Files To
DuckConvert is built with Next.js in static export mode (`output: 'export'`) and deployed as static files — there are no API routes, server actions, or file-upload endpoints anywhere in the app for a file to be sent to.
2. Verify It Yourself
You don't have to take our word for it — this takes about a minute to check in any browser:
- Open DevTools: Right-click anywhere on DuckConvert and select Inspect (or press F12), then open the Network tab.
- Load a file: Drag and drop a document (a CSV or PDF works well) into the dropzone.
- Go offline: Disconnect Wi-Fi or unplug your ethernet cable.
- Convert it: Pick an output format and click Convert. The conversion completes normally with no internet connection.
- Check the Network tab: No new requests should appear for your file — nothing was sent anywhere.
3. Open-Source Libraries In Use
The actual file processing is handled by well-known open-source libraries, run entirely client-side:
Video and audio transcoding, compiled to WebAssembly.
PDF rendering, parsing, and merging in the browser.
Client-side spreadsheet parsing for CSV, XLSX, and JSON.
In-browser Word .docx to HTML/Markdown conversion.