Where your file goes when you convert it here
Nowhere.
That claim is easy to make and just as easy to fake, so this page walks through the actual mechanism, then shows you two ways to catch us if we ever break it.
The pages are static, and that is the entire secret
When your browser asks our host for /pdf-to-csv/, it receives HTML, CSS, and JavaScript. That conversation is then over. The JavaScript it received contains the complete converter, so by the time you pick a file, the network's part in the story has already ended. There is no upload endpoint on this site. Not a hidden one, not a fallback one. The code that would receive your file was never written.
This is an old, boring architecture, and that is its charm. A static page cannot lose your data in a breach, cannot quietly change what it does between the audit and your visit, and cannot rack up server bills that tempt its owner into monetizing the files passing through.
Two ways to verify it, right now
The polite way: press F12, open the Network tab, and run any conversion. You will see the page load, a parser library arrive from a CDN, and then silence. No request carries your file, because no request is made after your file enters the picture.
The blunt way: load a tool, switch on airplane mode, and convert. It works. Whatever finished the job clearly was not a server.
Why it can afford to be free
Hosting static pages for a site this size costs less per month than a sandwich, and the expensive part of conversion — the computing — happens on your machine, not ours. Ads on the page cover the hosting. That arithmetic is the whole business model, and it is why there are no accounts, no tiers, no "3 free conversions remaining." Charging per file would mean building the upload infrastructure whose absence is the point.
What this architecture makes impossible
A conventional converter site holds a copy of every file its users trust it with: bank statements, contracts, unreleased design work. Its privacy policy is a promise about behavior. Ours is a description of plumbing. We could not read, sell, or leak your files even on our worst day, because they never arrive. The privacy policy is short for exactly this reason.
The rules the site is built under
A tool ships when it does the real work inside the tab, and honestly. This has teeth. There is no DWG→PDF converter here yet, although people search for one constantly, because no current in-browser engine reads DWG files well enough to trust. When the PDF tool meets a scanned statement, it tells you it does not do OCR instead of returning confident garbage. When the slicer produces G-code, it reminds you to review it before feeding it to a machine that gets hot and moves.
The engines are real and you can read them: Mozilla's pdf.js extracts the PDFs, Ultimaker's CuraEngine (compiled to WebAssembly) slices the STLs, Spotify's Basic Pitch neural network transcribes the audio, and @webtoon/psd parses the Photoshop files. FileKiln's contribution is the plumbing that lets them run where your data already lives.
Found something that behaves badly, or want a converter that is not here? A person reads [email protected].