We're building the web's most trustworthy collection of developer tools.
No uploads. No servers. Just code running in your browser.
FileMint started as a response to a security paradox I encountered during my high school computer science finals. I needed to merge several encrypted PDF documents, but every "online" tool I found required me to transmit those bytes to an unknown cloud server.
As a student developer obsessed with the low-level architecture of the web, I knew this wasn't necessary. Modern browsers are not just document viewers - they are high-performance computing environments. I realized that by combining React for the UI and Rust-compiled WebAssembly for the heavy lifting, I could build a tool that executes complex file logic entirely within the local V8 engine sandbox.
I built FileMint to prove that privacy is not just a policy - it is an engineering choice. By eliminating the back-end processing layer, I created a trustless system. I do not have to ask you to trust me with your data, because my code is architecturally incapable of seeing it. This zero-server-upload model is the core of our technical DNA.
"I engineered FileMint to bypass the centralized server paradigm. Your data stays precisely where it belongs: on your disk."
View Full Technical Bio →FileMint runs on a high-performance stack of React, Rust, and C++ compiled to WASM. I chose this architecture because browser-native execution keeps core processing local for many sensitive document workflows.
Traditional online tools rely on Python or PHP backends. My tools use near-native WASM modules to perform binary manipulation. This allows FileMint to handle memory-intensive tasks like extracting text from high-resolution images or flattening complex PDF page trees using only your local CPU power. It's clean, fast, and completely contained within your browser's memory space.
By leveraging the specialized File System Access API and local RAM buffers, my code performs heavy-duty byte manipulation without a single network request. Instead of multipath form uploads, we read files into ArrayBuffer objects, keeping your data strictly in your browser's private memory space throughout the entire lifecycle of the tool usage.
FileMint prioritizes privacy-preserving defaults. Core tool behavior is local-first, and non-essential analytics are consent-based. The goal is to keep functionality transparent and reduce unnecessary data collection.
AI Engineering Student & Privacy Architect
I'm a student developer dedicated to building the next generation of privacy-transparent tools. I believe the future of productivity lies in the browser, specifically through the use of client-side execution to bypass traditional, centralized data-collection models.
When I'm not studying for midterms, I'm usually digging into the V8 engine source or exploring how WebAssembly can be used to port high-performance desktop C++ and Rust libraries to the web. FileMint is my primary contribution to this vision of a more private, decentralized internet.
Built with privacy, speed, and user experience as our core principles
Everything happens right in your browser. I don't want to see your files, and my code literally can't send them anywhere. Your data stays on your device, just like it should.
Waiting for files to upload is the worst. Since this runs on your own computer, it's instant. Even huge PDFs or photos process as fast as your CPU can handle.
I'm a student, not a corporation. I built this to help people, so there are no paywalls, subscriptions, or "pro" versions. Just tools that work.
I hate signing up for stuff just to do one quick thing. You don't need an account or an email to use FileMint. Just open the page and go.
If you lose your Wi-Fi, the tools still work! Once the page loads, you can go into airplane mode and keep editing your files. Pretty cool, right?
Analytics are limited and consent-based. The product is focused on utility first, with transparent controls for non-essential scripts.
Try our privacy-first tools built with the same principles you just read about
