About BriskFile
BriskFile is 57 file tools that run entirely inside your browser, paid for by advertising and nothing else. No file you open here is uploaded, because there is no server to upload it to — and you can confirm that yourself in about ten seconds.
This page exists because a tool site that will not say who runs it, or how it is funded, has not earned the right to be trusted with a contract or a passport scan.
The one thing that makes this different
Almost every free file converter on the web works the same way: you upload your file, a server somewhere does the work, and you download the result. That model is why those sites can afford to be free — the file is the product — and it is why their privacy policies are worth reading slowly.
BriskFile does the work in the tab you already have open. The image codecs and the PDF engine are compiled to WebAssembly and run on your own processor. The practical consequence is not a promise but an architecture: there is no upload endpoint, no storage bucket and no retention period, because there is nowhere for a file to go.
The claim is deliberately one you can check rather than one you have to believe. Open the Network tab in your browser's developer tools and convert something — nothing leaves. Or load a tool page, switch your wifi off, and use it anyway.
How it pays for itself
Advertising. That is the entire model, and we would rather write it down than let you wonder.
There is no paid tier, no watermark to remove, no daily limit to lift and no account to create. Those are the four things free file tools normally use to convert visitors into customers, and BriskFile has none of them — partly because they are unpleasant, and partly because an account would mean holding data about you, which cuts against the only thing this site is really offering.
What that means in practice is that the adverts have to be tolerable rather than aggressive. Their space is reserved in the layout before anything loads, so an advert can never push the button you were about to press. That is a technical commitment as much as a design one, and it is measured in the build.
How the tools are built
Every tool is written against the relevant specification and, wherever an independent implementation exists, checked against it rather than against itself. That distinction matters more than it sounds: a converter tested only with its own reader proves that two halves of the same misunderstanding agree with each other.
| Area | Checked against |
|---|---|
| PDF encryption and passwords | pypdf |
| Dates, time zones and ISO week numbers | Python's datetime |
| Base64 encoding | Node's Buffer |
| Barcodes and QR symbols | Established reference encoders |
| Colour contrast | The worked examples in WCAG itself |
Where a tool has a known limit, the page says so. The passport photo specifications link to the government source they came from; the PDF text extractor tells you plainly when a document is a scan with no text in it; the electronic signature tool states that it is not a cryptographic one. A tool that overstates what it does is worse than one that does less.
Who writes it
BriskFile is published by BriskLabz, a small team writing under that name rather than individual bylines.
That is a pseudonym, and we would rather say so than let you work it out. It is not there to make the site seem larger than it is, and it is not a way of dodging responsibility — hello@briskfile.com reaches the people who write the code, and corrections get published rather than quietly absorbed. The reason is simply that the promise this site makes is about how the software behaves, and you can check that from your browser's Network tab regardless of whose name is at the bottom of the page. A legal name would tell you nothing you could verify.
If something here is wrong, we would genuinely like to know — a file format edge case we have mishandled is worth more to us than a compliment. hello@briskfile.com reaches us, and the contact page has the rest.
What it does not do
There is no API, and there cannot be a useful one: calling an API means sending us the file, which is the single thing this site is built not to do. There is no desktop application. Nothing is stored between visits beyond the settings your browser keeps for you.
It is also not an offline application, and we are careful about that wording. Once a tool page is open it makes no further request and will keep working with the network off — but the page itself still has to arrive from somewhere the first time.
Questions
How does BriskFile make money if everything is free?
Advertising, and nothing else. There is no paid tier, no upsell and no account to create. We would rather say that plainly than have you wonder what the catch is — the catch is the adverts, and they are the whole of it. Nothing about your files is sold, because nothing about your files ever reaches us to sell.
How can you be sure nothing is uploaded?
You do not have to take our word for it, which is the point. Open your browser's developer tools, switch to the Network tab, and convert something. No request carries your file, because there is no server to carry it to — the conversion runs on your own processor. If you would rather test it more bluntly, turn off your wifi after the page has loaded and use the tool anyway.
Who writes the tools?
BriskFile is published by BriskLabz, a small team writing under that name rather than individual bylines. Every tool is written against the file-format specifications and checked against an independent implementation wherever one exists — the PDF encryption against pypdf, the date handling against Python's datetime, the barcodes against established encoders. Where we got something wrong, we say so in the page rather than quietly fixing it.
Can I use BriskFile for confidential documents?
That is what it is for. Contracts, medical records, passports, unpublished manuscripts and anything under embargo are exactly the files that should not be posted to a stranger's server, and they are the reason this site processes everything locally. The usual caveat applies: the security of your own device is still your own.
Do you have an API?
No, and there is a structural reason why not. An API means sending us the file, which is precisely the thing this site exists not to do. The engine is ordinary JavaScript and WebAssembly running in your tab; there is no server-side version of it to call.
What BriskFile will not do to you
-
Your files never leave your device
Every conversion runs in your browser. Open DevTools, watch the Network tab, and you will see no upload — because there is not one.
-
No account, no email, no watermark
Nothing to sign up for and nothing stamped on your images. There is no step between choosing a file and getting it back.
-
No limits at the download button
No daily cap, no file counter, no "upgrade to download". If the tool starts a job, it finishes it.
-
Checkable, not just claimed
Open the Network tab and convert something — nothing goes out. Or load the page, disconnect, and watch it keep working: the tool is already on your machine, and your file never leaves it.