Why freelancers should care where their invoices are processed
Invoices contain client names, addresses, rates and sometimes tax IDs. When you merge them with a typical online converter, the files are uploaded to somebody else's server first. FileForge never does that: every operation runs inside your browser tab, and you can verify it yourself by opening DevTools → Network while a tool runs — you'll see zero file traffic.
Scenario: end-of-quarter invoice bundle
- Export each invoice as a PDF from your invoicing app.
- Open Merge PDF, add the files, and drag them into chronological order.
- Download one combined archive-friendly PDF for your records — nothing was uploaded anywhere.
- Need to pull out just the pages you sent to one client? Split PDF extracts custom ranges like
1-3, 7.
Scenario: receipt photos into one expense PDF
- Photograph receipts, then open Images to PDF.
- Add up to 30 JPG/PNG/WebP photos, order them, pick A4 or Letter (or fit-to-image).
- Convert and download a single tidy PDF for your accountant.
- If the bundle is too big to email, Compress PDF can shrink it — note that this rasterizes pages, so use High quality for readability.
Quick data fixes without installing anything
Client sent a CSV but the importer wants JSON? CSV ↔ JSON handles it locally. Need to check a suspicious file before opening it? File Hash gives you checksums to compare. Cleaning up exported data? JSON Formatter makes it readable.
The privacy habit
You don't need a policy memo to be safe — just make it a rule that client financial documents only pass through tools that physically cannot upload them. Every FileForge tool qualifies, because the upload code doesn't exist.