Introducing ShrinkFox by Chovexa — 100% Private In-Browser Media Compressor

Most online file compression tools require uploading sensitive images and documents to remote cloud servers, which introduces privacy risks, bandwidth lag, and strict file size paywalls.

To solve this, Chovexa engineered ShrinkFox — a fast, free, and privacy-first web utility built to compress images (JPG, PNG, WebP) and PDF documents entirely inside your browser.

Zero-Server Uploads: By leveraging client-side Canvas and WebAssembly technologies, ShrinkFox processes every file locally within your device's memory. Zero bytes leave your machine, ensuring total data confidentiality.

Strict Target Size Control: Dial in exact target file thresholds (KB/MB) required for official portals, job applications, or web optimization without trial-and-error quality loss.

Batch Multi-Format Optimization: Process multiple image formats and multi-page PDFs simultaneously with instant local downloads.

ShrinkFox by Chovexa is completely free to use with no hidden subscriptions or file limits.

Try the tool live: https://shrinkfox.chovexa.dev/

Explore the ecosystem: https://shrinkfox.chovexa.dev/

Comments

[Amit Feldman]

Fully client-side compression is the right call for a privacy pitch — "your files never leave the browser" is only believable when there's no upload endpoint to take your word for, and building it that way from day one is harder than bolting on a privacy policy later.

Ran a passive check of the site while reading (public response headers and homepage HTML only — nothing a first-time visitor's browser doesn't see). One finding looks time-sensitive:

• Your canonical host is dead. The page declares , og:url points there too, robots.txt lists Sitemap: compress.chovexa.dev/sitemap.xml, and every URL inside the sitemap itself is on compress.chovexa.dev — which currently has no DNS record at all. The sitemap's lastmod is today, so this looks like a subdomain rename (compress -> shrinkfox) where the SEO tags didn't come along. Until it's fixed, search engines will try to consolidate your page onto a host that doesn't resolve. One search-and-replace across the canonical link, og:url, robots.txt Sitemap line, and the sitemap entries fixes it.
• Strong baseline otherwise: title, meta description, Open Graph, H1, robots.txt, and a valid XML sitemap are all present — better launch shape than most.
• Header gap: 5 of the 6 baseline security headers are missing (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). On Vercel that's one headers block in vercel.json; CSP can ship report-only first so nothing breaks. HSTS is on but lacks includeSubDomains, so subdomains aren't covered.
• Minor: access-control-allow-origin: * on the HTML response is harmless for a static page, just worth scoping if you ever add an API.

Happy to re-run the check free if you ship fixes and want a before/after.