
You already own the photos. They are larger than they need to be.
file.rocks is the UI. Optimize photos compresses and resizes in the browser, then re-uploads to the same key. That overwrites the original object.
This is not how to clean up near-duplicate photos in your own bucket or how to clean up likely duplicates in your own bucket. Those remove copies. This shrinks the file you keep.
You need S3-compatible object storage. Not another Drive clone.
If you do not have a bucket hooked up, follow how to connect a Backblaze B2 bucket and come back. For the price table, see the cheapest cloud object storage comparison.
Sign in at file.rocks. Open Settings → Cleanup. Pick the bucket if needed.
Open Optimize photos.
Set the run:
Click Continue to select photos.
Pick candidates (Select all / Select none / Reload).
Open Review overwrite. Ack that this overwrites the original. Type OVERWRITE. Click Overwrite originals.
Toast shape: Optimized N photos · saved ~X.
Honest bits: same-key overwrite. No separate undo from this tool. If Automations Trash is on, discarded bytes may land there. Do not invent a Restore button on this screen.
This is not visual near-duplicates. Burst shots stay in how to clean up near-duplicate photos in your own bucket.
This is not exact-hash duplicates. That is how to clean up likely duplicates in your own bucket.
This is not row Delete in Files. That is how to delete a file from your own bucket.
This is not the Files preview player. That is how to preview a file in your own bucket.
Need near-copies gone instead of smaller originals? That is how to clean up near-duplicate photos in your own bucket.
Need exact hash twins gone? That is how to clean up likely duplicates in your own bucket.