Prepare Photos from Storage to Website
Prepare your photo batch for a website: name the files, correct capture dates and adjust image dimensions and file size. Plan alt text and share a contact sheet so your client can choose photos.
Your progress is stored only in your own browser (localStorage) and is not transmitted to our servers. Third-party resources (e.g. advertising and analytics from Google/Cloudflare) may transfer data when loaded.
This workflow guides you through the following steps:
- 1. Give the batch consistent names Rename photos by project, date and counter, then download the ZIP with its CSV list. Your originals stay untouched.
- 2. Correct capture dates If the camera clock was wrong, shift the batch's EXIF timestamps or set an absolute date.
- 3. Resize for the web Resize the images to your website's target dimensions, handling portrait and landscape photos separately.
- 4. Reduce file size Compress the resized images to meet your load-time targets and check quality in the preview comparison.
- 5. Plan alt text Take each image through the decision tree: decorative or informative. Check length and wording, then export the CSV and HTML snippets.
- 6. Share the selection with your client Arrange the photos in a contact sheet with filenames so your client can refer to image numbers instead of filenames.
Interactive workflow loading …
What you get at the end
A consistently named, correctly dated and optimized batch of images with finished alt text and a contact sheet for selecting photos.
Why these steps in this order
Consistent names and correct dates come first, then dimensions and file size, then accessibility. The contact sheet lets clients choose photos without a file manager.
More background
Formats, rights, metadata and load time
Frequently asked questions
Where is my data stored?
Your playbook progress is saved in your own browser using localStorage. Nothing you enter is uploaded to our servers. Clearing your browser data resets the workflow.