Viktor.comAn AI coworker that actually does the work
PixelVault
Process, Edit & Protect Images. Free and private
13 followers
Process, Edit & Protect Images. Free and private
13 followers
An image toolkit that runs completely in your browser. Compress, convert, resize, crop, rotate, edit, add watermark, blur, and clean metadata from images. 100% free — no ads, no accounts, no paywall 100% private — runs in your browser, images are never uploaded to a server
does the metadata removal actually strip exif and gps data fully, or just some of it? also curious how it handles really large files like 50mb plus without choking the browser
@enginmoro hey Engin in terms of big files 50MB are no problem for single or batch, but bigger could be a challenge indeed - what matters most is the pixels that cost memory. A 50MB photo is usually 40-60 megapixels, which is comfortably fine. Browsers top out on different amount, i think for Chrome it's 268 megapixels. I tried to implement the app in a way that in never hangs or crashes, rather shows error message if it can't process file too big. But yeah there's a limit that will not get processed. As a workaround resolution can be reduced and processed again (i tried to add hints and messages for such cases).
ps in a batch - images load one at a time with a progress row, so a batch of big photos won't choke.
shotly about metadata - everything is removed. GPS lives inside EXIF, and the whole EXIF gets removed (unless something is unchecked). also XMP, IPTC, the embedded thumbnail, comments, C2PA credentials, and anything hidden after the end of the image. Only the color profile stays — that's just sRGB, no private info.
How does it actually handle really large files like 50MB RAW images? Worried it might choke since everything has to run locally on my machine.
@nevinbavbek heey thanks for asking, RAW (CR2, NEF, ARW, DNG) is sadly not supported - browsers don't decode them locally, thus it would require sending to server and compromise security :(
Though 50MB files are no problem - what matters most is the pixels that cost memory, not file size. A 50MB photo is usually 40-60 megapixels, which is comfortably fine.
Browsers top out on different amount, i think for Chrome it's 268 megapixels. I tried to implement the app in a way that in never hangs or crashes, rather shows error message if it can't process file too big.
in a batch - images load one at a time with a progress row, so a batch of big photos won't choke.
i hope this answers ur question and let me know if there's more 😊
runs really smooth, resized a batch of photos without any upload wait and the metadata stripper is a nice touch most tools skip.
@grkem86fq 🧡