A lot of small file jobs still follow the same awkward pattern: 1. choose a file, 2. upload it to someone else's server, 3. wait for processing, 4. download the result. For some tasks, that server round trip is unnecessary. I have been building **FileNest Worktools** , a browser-based toolkit for repetitive file work, around a simple constraint: > If a task can reasonably be done inside the browser, the file contents should stay on the user's device. ## What currently runs locally The current FileNest tools cover: * batch file renaming * sequential, reverse, and custom-order renaming * JPG / PNG / WebP conversion * image resizing and compression * image-to-text OCR with editable review * PDF merge, split, extract, and images-to-PDF * text export to DOCX, PDF, TXT, Markdown, and HTML * CSV / TSV / JSON conversion * duplicate-file detection For these current browser-local workflows, the file contents are processed on the device rather than being sent to a conversion server. ## Why local processing matters Privacy is one reason, but it is not the only one. Many file operations do not actually need server-side infrastructure. Renaming a file is mostly about filenames, order, extensions, and conflict checks. Image resizing can be handled with browser APIs. CSV and JSON conversion is essentially local parsing and serialization. Duplicate detection can compare file fingerprints locally. If those jobs can stay inside the browser, there is less network overhead and one less copy of the user's files being created somewhere else. ## I also wanted the risky parts to stay visible One thing I dislike about many online file tools is the "click and hope" workflow. So I tried to make FileNest show more information before or after processing: * renamed files can be previewed before packaging * original files are not silently overwritten * image compression reports actual output bytes * duplicate detection uses content matching rather than filename guesses * OCR output can be reviewed and edited * the image enhancer does not claim that sharpening can recreate detail that never existed The goal is not to make file work exciting. It is to make repetitive file work less opaque. ## Where browser-local processing does _not_ fit Local processing is not automatically the right answer for every feature. Large AI models, heavy cloud rendering, collaborative workflows, or operations that require server-side storage may still need remote infrastructure. So I am deliberately avoiding the claim that every future FileNest feature will always be local-only. The current boundary is simpler: **the current file-processing tools are designed to keep file contents on the user's device where the workflow supports it.** ## The project FileNest currently has an English and Chinese interface. You can try it here: **https://filenest-pages.pages.dev/en** Some direct tools: * Batch file renamer https://filenest-pages.pages.dev/en/tools/batch-file-renamer * Image converter https://filenest-pages.pages.dev/en/tools/image-batch-converter * Local image OCR https://filenest-pages.pages.dev/en/tools/image-to-text-ocr * PDF tools https://filenest-pages.pages.dev/en/tools/pdf-batch-converter * CSV / JSON converter https://filenest-pages.pages.dev/en/tools/csv-json-converter ## Feedback I would actually find useful I am especially interested in: * browser compatibility problems * mobile usability problems * workflows that feel confusing * whether the privacy explanation is clear enough * repetitive file tasks that are still missing If you regularly use online file utilities, I would be interested to know which operation still makes you jump between too many tools.