As a blogger, I got tired of one specific problem: prepping images before every post.
Every time I wanted to publish, I'd end up bouncing between three or four different tools — one to compress the file size, another to convert formats, another to strip EXIF metadata, and yet another to clean up backgrounds. It ate up 10-15 minutes per post, every single time.
So I built PixPrep — a free, browser-based tool that handles the entire image-prep workflow in one place.
What it does
Compress — reduce file size without noticeable quality loss
Convert — switch between JPG, PNG, and WebP
Remove EXIF data — strip hidden metadata before publishing (good for privacy)
Remove backgrounds — clean cutouts, instantly
Why I built it this way
Most tools out there (TinyPNG, Squoosh, Remove.bg) are excellent, but they each solve one piece of the puzzle. I wanted something that covered the whole pre-publish workflow without needing to sign up or install anything — just open the browser and go.
It's built with a simple stack: PHP on the backend, HTML/CSS/JS on the frontend. Nothing fancy, just fast and functional.
Try it
It's live and free to use: https://pixprep.online/
Would genuinely love feedback from this community — especially if you're a blogger or content creator who deals with this same workflow headache. What would you want added next?
Top comments (1)
"Remove EXIF metadata in the browser" is a genuinely useful niche — bloggers rarely think about how much EXIF leaks (location, device, timestamps) until someone points it out.
One finding from a quick header scan of pixprep.online: HSTS and Content-Security-Policy are both missing (plus X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Your SEO basics are all clean — title, meta, h1, robots, sitemap — so this is the one gap left. The reason CSP matters specifically for you: your pitch is "everything stays in your browser," and CSP is the header that enforces that promise — without it, any injected third-party script can phone home and you'd never know.
You're on LiteSpeed shared hosting, so this is a five-line .htaccess block (Header always set ...) — no PHP change, takes effect immediately. Start CSP in Content-Security-Policy-Report-Only mode for a day so you can see what it would block before enforcing.
Happy to re-scan after it's live.