The Core Concept
A few weeks ago, I launched NeatKit—a suite of free web utilities aimed at solving a common frustration: having to upload sensitive files (like PDFs, images, and now videos) to random cloud servers just to perform basic tasks like compressing or trimming.
From day one, the architecture was 100% client-side. The browser does all the heavy lifting using local processing power. But yesterday, after crossing the 45-commit mark on the repo, I finally took the architecture to its logical conclusion: NeatKit is now an officially installable Progressive Web App (PWA) that works completely offline.
Why Local-First + PWA is a Game Changer for Utility Tools
Most online file converters follow a traditional client-server model:
- You upload a 50MB video file.
- The server processes it (and keeps your data in a cache somewhere).
- You download the processed file.
This model is slow, terrible for data privacy, and burns through internet bandwidth. By leveraging modern browser APIs and WebAssembly, NeatKit bypasses the server entirely.
By upgrading the platform to a PWA with aggressive service worker caching, you can now literally turn off your Wi-Fi, open the app, and it will still compress your videos or merge your PDFs perfectly.
What’s New in the App?
Along with the PWA upgrade, I just shipped three new intensive, browser-based video tools that run entirely client-side:
Video Compressor: Shrink mp4/webm files directly in your tab without burning upload data bundles.
Video Trimmer: Fast, frame-accurate cuts using local browser processing.
Video to GIF: Convert clips into high-quality GIFs instantly without watermarks.
Because it happens locally, a 100MB video uses 0MB of internet data to process. You only use data to load the website the very first time.
Lessons Learned & Challenges
Setting up the service workers to handle heavy media processing assets offline was a massive headache. Ensuring that the caching strategies didn't choke when dealing with large file buffers in the browser tab required a lot of trial and error (hence the jump to 45 commits!).
I’m currently mapping out the next phase of development. If you are a developer who hates clunky, ad-ridden web tools, I’d love for you to test this out.
Try installing the PWA, kicking your device into airplane mode, and seeing if you can break it.
I’m wide open to critiques on the architecture, UI improvements, or suggestions on what utility tool I should build client-side next!
Check it out here: neatkitapp.com
