Camera and card workflow
After a shoot, the operator copies the card into a fixed material folder on the Mac. That folder already contains the images intended for the next processing pass.
Folder-based batch image processing
Use the whole folder as the batch
A shoot already ends in a directory. Select it once and SizeFold uses its top-level images for crop, color, output, naming, and original archiving.
Memory card importsTethered capture foldersRecurring team handoffs
Why use a folder?
The folder already defines the batch
A card import and a tethered shoot both finish in a directory. Selecting the same files again adds work and another chance to miss or repeat an image.
Tethered shooting workflow
A tethering application writes each capture into one configured directory. The same location can feed SizeFold without another import step or photo library.
File selection repeats the decision
Many tools open the folder and still ask which files belong to the batch. That extra step can miss an image or pull in one that was already processed.
The next batch
When one batch leaves, the folder is ready again
SizeFold remembers the directory and its enabled recipes. Put in new photos and run the saved settings again.
Photos enter the folder
Copy the next card or let the tethering app continue writing to the same location.
Review the current batch
The supported images at the folder top level appear together for inspection.
Run the saved workflow
Apply the crop, size, color, naming, and output recipes already configured.
Make room for what is next
Successful originals move to the archive and processed images go to their destinations.
Version note: the Mac App Store build currently under review uses Scan for New or ⌘R. Automatic refresh while SizeFold is open is developed for the next update; it refreshes the pending list but does not start processing by itself.
Failure handling
A source leaves only after its outputs succeed
SizeFold keeps the original in the input directory until every enabled recipe has written its file.
Top-level images form the batch
SizeFold reads supported JPG, PNG, HEIC, and TIFF files at the top level. It does not recursively pull unrelated images from nested output and archive folders.
All enabled recipes complete first
One source image may need several crops or looks. SizeFold confirms every required output before it moves that original out of the input directory.
A failed source stays ready to retry
If output or archiving fails, SizeFold removes the incomplete products from that attempt and leaves the source image in place.
Common questions
Working from a folder with SizeFold
Does SizeFold process every file in subfolders?
No. The current batch consists of supported image files at the top level of the chosen input directory.
Can I use a tethered capture directory?
Yes. Choose the directory where the tethering application writes new photos and use it as the SizeFold input folder.
Do I choose individual images before running?
No. SizeFold is designed around the complete directory as the batch scope rather than a per-run file selection.
Where do successful originals go?
The current release uses an Originals folder inside the input directory. A separate custom archive directory is developed for the next update.
Use the same folder for the next batch.
The saved recipes are ready when new photos arrive.