Productivity2026-07-21

I Replaced My Entire Image Workflow With Browser Tools

I used to juggle Photoshop, Sketch, and a handful of random desktop apps just to get my images ready for the web. Then I realized my browser could do it all — and do it faster.

I used to have a whole ritual for processing images. Open Photoshop. Wait for it to load. Crop. Export for web. Realize the dimensions are wrong. Resize. Wait again. Compress with ImageOptim. By the time I had a single hero image ready, I'd already context-switched four times and lost whatever flow I was in. This is the story of how I killed that ritual and replaced it with three browser tabs. It started with image compression. I was building a landing page and the Lighthouse score was tanking because my hero image was something like 2.4MB. I opened maybe six different compression tools before I found one that worked right in the browser. No upload to a server. No file size limit. Just drag, drop, download. That moment — when I saw a 2.4MB file drop to 180KB with no visible quality loss — was the first domino. The next week I needed to resize a batch of product photos. All of them needed to be exactly 1200 pixels wide. Normally this means either writing a shell script with ImageMagick (which I always have to look up the syntax for) or opening each file individually in some editor. I found a browser-based resize tool that handled the whole batch at once. Set the width, uploaded all twelve files, and downloaded them a few seconds later all uniformly sized. I think I sat there staring at the screen for a good ten seconds, genuinely annoyed at all the times I'd done this manually. Cropping was the last piece. I'm picky about composition. I usually want to frame things a specific way, so I assumed I'd always need a proper editor for that. But the browser crop tool I landed on gives you a live preview with drag handles and preset aspect ratios. It's honestly faster than Photoshop's crop tool because there's no layer management, no canvas resizing, no accidental background layer locks. Just select the area and export. Here's the workflow that emerged without me really planning it: Crop first, resize second, compress last. That order matters because cropping changes the pixel dimensions, resizing brings everything to a consistent spec, and compression strips the remaining fat. If you compress before resizing, you're wasting effort on pixels you're about to throw away anyway. I do all three in the browser now. The whole pipeline takes maybe two minutes per batch of images. And the best part? I don't have to install anything, update anything, or pay for a Creative Cloud subscription. These tools are just URLs. They don't send my files to a server — everything processes locally in JavaScript — so there's no privacy concern with client work either. For a while I felt guilty about it. Like I was cheating by not using "real" tools. But that's nonsense. The browser has become a legitimate runtime for creative work. WebAssembly, Canvas APIs, modern JavaScript — they're not toys anymore. They're production tools that happen to live in a tab. I still use Photoshop occasionally for things like masking or color grading. But for the 90% of my image work that's just crop-resize-compress, the browser does it better, faster, and with less friction. And honestly? Not having to stare at Photoshop's loading screen ten times a day has done wonders for my mood. If you're still using desktop software for basic image processing, try doing it in the browser for a week. You might not go back.