what_you_need
Prepare the inputs before opening the apps
- Approved master images
- Current platform dimension requirements
- Crop priorities for faces, products, and text
- Destination folder naming
step_by_step
The working process
-
1
Verify current channel requirements
Platform specifications change. Confirm the formats and placements you are actually publishing before creating presets or output folders.
-
2
Protect the master set
Keep one approved source folder. Every platform version should be reproducible from those masters rather than resized from an already resized copy.
-
3
Create one channel batch at a time
Use Batch Resize Image with the target dimensions and crop behavior. Write each result to a clearly named platform folder.
-
4
Inspect sensitive crops
Review images containing faces, products, logos, and on-image text. Automatic crop rules cannot know what is semantically important.
-
5
Test in the publishing interface
Upload a small sample or preview it in the platform’s composer. Feed corrections back into the resize setup before processing future campaigns.
human_checkpoint
Review before you call it finished
- Were current platform requirements verified?
- Did every output come from the master set?
- Are important subjects preserved in the crop?
- Are platform folders unambiguous?
honest_boundaries
Limits and privacy
Practical limitation
One composition cannot always be adapted cleanly to every aspect ratio. Some images need manual crops or a separately composed version.
Privacy boundary
Resizing happens locally. Platform upload occurs only when you choose to publish.
faq
Questions worth answering
Can I use one preset forever?
No. Platform recommendations and placements change, so verify current requirements when a campaign matters.