Image File Names and Privacy
A clean image can still leak context through its file name. Before uploading public copies, check whether the name contains a client, project, location, date, account, or internal workflow label.
Look for names added by apps
Phones, cameras, design tools, and ticket systems may create names that include dates, exports, project names, or editing history. Those names can travel with the file.
Avoid client and account names
Do not upload images named after customers, organizations, email addresses, case IDs, or internal dashboards unless that context is meant to be public.
Use simple descriptive names
For public copies, use short neutral names such as product-front.jpg, screenshot-error-state.png, or proof-watermarked.webp.
Rename after export
If you resize, compress, convert, or watermark an image, rename the final copy rather than relying on the original source name.
Keep a private archive separately
If you need detailed naming for internal records, keep it in private storage. The shared copy should use a public-safe name.
Related tools
Image Converter, Image Resizer, and Image Compressor all help create new public copies that can be renamed before sharing.