I built 70+ browser-based file tools. Here's what I learned.

Over the past several months, I've been building ToolsRoot, a platform with 70+ browser-based tools for PDFs, images, documents, audio, video, and archives.

The biggest surprise wasn't the engineering—it was discovering how many everyday file workflows are still surprisingly frustrating.

People often have to:

• Visit multiple websites for different file types.

• Wait for uploads before anything happens.

• Create accounts just to complete a simple task.

• Worry about where their files are stored afterward.

That made me wonder whether modern browser technologies have reached the point where many of these tasks can happen directly on the user's device instead.

Building around that idea came with plenty of technical challenges, but it also changed how I think about privacy, performance, and user experience.

I'm curious how other makers think about this.

• If you've built browser-based applications, what challenges surprised you?

• Do you prefer local browser processing or cloud processing, and why?

• What's the most frustrating file-related workflow you've encountered that still feels unnecessarily complicated?

I'd love to hear your experiences and learn how others have approached similar problems.