https://bulkresizeimages.online/
all these tools process image just in browser and never upload images to any server.
And more tools in the kitchen
11–20 of 39 posts
https://bulkresizeimages.online/
all these tools process image just in browser and never upload images to any server.
And more tools in the kitchen
Congrats on shipping. However, the "Privacy First" and "No Ads" claim gets eroded pretty quickly by cookies, and requests to trackers like n.clarity.ms, google-analytics and adtrafficquality.google. Note - I don't actually have an issue with any of those things - if you wanna monetize this service through analytics and ads, that's up to you. But it's at odds with your privacy first claims.
Congrats on shipping. However, the "Privacy First" and "No Ads" claim gets eroded pretty quickly by cookies, and requests to trackers like n.clarity.ms, google-analytics and adtrafficquality.google. Note - I don't actually have an issue with any of those things - if you wanna monetize this service through analytics and ads, that's up to you. But it's at odds with your privacy first claims.
Congrats on shipping. However, the "Privacy First" and "No Ads" claim gets eroded pretty quickly by cookies, and requests to trackers like n.clarity.ms, google-analytics and adtrafficquality.google. Note - I don't actually have an issue with any of those things - if you wanna monetize this service through analytics and ads, that's up to you. But it's at odds with your privacy first claims.
Yeah, I made a local image compressor/converter for myself that's actually private: https://github.com/blopker/alic
upload... no uploads...
The FileReader web API enables you to make local files available to content running in the browser. This entails a file picker and, depending on the verbiage in your browser UI, that may talk about "upload." That doesn't mean anything is being sent anywhere. See MDN: https://developer.mozilla.org/en-US/docs/Web/API/FileReader (Or that nothing is; I have not audited this code. But I vouched the parent comment to point…
Maybe I should not use the text ’upload’ to avoid the confusion
I build cool image tools: Here is another two tools you may found helpful https://bulkresizeimages.online/ https://resizeimage.dev/ all these tools process image just in browser and never upload images to any server. And more tools in the kitchen
I build cool image tools: Here is another two tools you may found helpful https://bulkresizeimages.online/ https://resizeimage.dev/ all these tools process image just in browser and never upload images to any server. And more tools in the kitchen
https://squoosh.app/ has long been my go-to. UI is fantastic for letting me do the thing I most often am looking for, shrinking down large image files.
Earlier quoted context omitted.
The FileReader web API enables you to make local files available to content running in the browser. This entails a file picker and, depending on the verbiage in your browser UI, that may talk about "upload." That doesn't mean anything is being sent anywhere. See MDN: https://developer.mozilla.org/en-US/docs/Web/API/FileReader (Or that nothing is; I have not audited this code. But I vouched the parent comment to point…
Great explanation! Maybe I should not use the text ’upload’ to avoid the confusion