Urgent.News

What's breaking now, across thousands of outlets.

Tech

I Got Tired of “Free Tools” That Upload My Files — So I Built Browser-Only Ones

Most “free online tools” ask you to paste text or upload a photo. What they don’t always make clear: that content often leaves your device. For JSON with client data, a JWT, a draft you’re not ready to publish, or a passport-style photo — that’s a bad trade. So I built KeptTools : a small set of developer and image tools that run in the browser. No account. No “upload to process.” 👉…

Many online utilities ask you to share your files or photos, often without disclosing that your data may leave your device. For sensitive information like JSON with client data, a JSON Web Token, a draft you haven't published yet, or even a passport photo, this is a risky exchange. That's why I created KeptTools – a collection of developer and image tools that run directly in your browser. No account is required, and there's no need to upload files for processing.

When you visit a KeptTools page, everything happens on the page itself using JavaScript. You can format, convert, crop, or decode your content without creating an account, and closing the tab will end the session – your files won't be stored on our servers.

Some tools download a small model the first time you use them, such as for portrait background replacement. This download is the model, not your photo.

These tools are designed for developers and image manipulation. Some of the features include:

- JSON formatter and validator

- JSON converter (CSV, Laravel, TypeScript, PHP, etc.)

- SQL formatter

- JWT decoder

- Base64, hash, URL/HTML encoding

- Regex testing

- Cron generator

- UUID and slug generation

- Image tools (PNG/JPG to WebP, compressing, cropping, converting to SVG, changing backgrounds)

- Text utilities (word counter, case converters)

And more on the site.

I rely on these tools regularly, and I don't want any random website to keep a copy of my token, JSON data, or even an ID photo. Privacy shouldn't be a premium feature for basic tools.

The stack behind these tools is short: Laravel + Vite + Tailwind + Alpine. The tools are client-side whenever possible.

I'm interested in your feedback on the browser-only / no upload approach. Is it a strong enough reason for you to switch to these tools? Which one would you try first when you land on the homepage? What features are missing that would make you leave? If something isn't clear, let me know, as I'm iterating based on real user experiences. You can find KeptTools at https://kepttools.com.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Test Your supabase-js Code Without a Server: An In-Process Backend for Vitest

Most Supabase apps end up with one of two testing strategies: Mock supabase-js . Fast, but the mocks test what you think the database does. RLS, constraints, and defaults never run.

  • In-process backend runs within test process, no server needed
  • Uses Vitest and tinbase for JavaScript testing and Supabase compatibility
  • tinbase provides backend.fetch function for supabase-js requests

Concurrency Programming (10): How BlockingQueue and Channels Work — From Runtime to CPU

Table of Contents 0. What Does This Article Answer Next? 1. How Does the JDK Implement ArrayBlockingQueue? 1.1 Layers 1.2 End-to-End Implementation Path for put / take 1.3 Guarantees at the Runtime /…

  • Java's ArrayBlockingQueue uses ReentrantLock for atomicity
  • Go's channels achieve atomicity via lock (chanlock)
  • Hardware layer ensures visibility and ordering through cache coherence and memory fences

More from Thursday 15 October →