Commerce, catalogue and merchandising teams · no signup
Product image publish prep
Prepare a product image for a storefront or catalogue with a local crop and bounded output width.
Use the commerce-specific crop first, then downscale the final composition once so you avoid resizing pixels that will be discarded.
The builder stores route slugs only. It does not carry pasted text, uploaded files or generated results between tool pages.
Outcome-first sequence
The order is curated around the job, not around a product feature menu.
Explicit data boundary
Each atomic tool keeps its own runtime and privacy truth. A recipe never silently moves your payload.
Canonical tools only
Every step resolves against the live free-tool catalog, so stale recipe routes fail closed in code.
Recipe · 2 verified steps
- 1Open step
Frame the product
Product Image Cropper
Remove irrelevant edges and set the final product composition before resizing.
Commerce · Cropper.js · MIT
- 2Open step
Bound upload width
Image Max-Width Resizer
Downscale the cropped image to a practical maximum width while preserving aspect ratio.
Images · Pica · MIT
When the job repeats
Keep one-off work free. Escalate only when repetition creates value.
If this becomes a recurring workflow that needs monitoring, evidence, team controls or support, compare the paid workflow products instead of paying to unlock the atomic utilities.
Pass the useful route forward
Share this workflow, not visitor data.
Native share sends only this canonical Solarc route plus public page context. It never includes tool inputs, generated results, uploaded files, local presets or builder state.