Batch jobs

A batch is one setting applied to many local files. Shrynk does not upload the folder. The browser tool cannot do this — tab memory and the 100MB cap make it a one-clip preview only.

When batch is the right tool

A camera-roll dump of MOV/MP4 you want as smaller MP4s.
A course of screen recordings that should all use CRF 23.
A docs folder of Markdown that should all become DOCX or HTML.
A set of WebP exports that an old CMS will only accept as JPG.

Convert batches

Pick exactly one pair (for example webp → jpg or md → docx).
Drop many files or point at a folder. Mixed extensions that do not match the source side are skipped or rejected.
Set options once. Every file in the run gets the same JPEG quality, delimiter, bitrate, or CSS flag.
Start. History stores success/fail counts and the output directory.

Need two different settings (screen recordings vs talking-head)? Split into two folders and run twice. One run, one preset — that is how output stays predictable.

Compress batches

Same idea on the Compress tab: one quality preset or one target size for the whole list. Multi-file compress requires Pro. A single file still follows the 100MB Free rule.

Per-file speed is roughly the same as a one-off encode. You save the babysitting, not a secret faster codec.

Free vs Pro

The product UI treats more than one file as a Pro job for both convert and compress. Free is for trying a pair or shrinking one clip. The $9 license is perpetual for that machine’s activations under the current store rules — see Free vs Pro.

Practical layout on disk

Keep originals in a read-only folder. Write output next to input or to a sibling out\ directory so you can diff sizes.
Do not run a second compress pass on yesterday’s output unless you changed your mind about CRF. That is generation loss.
For “convert then compress,” finish convert, spot-check playback, then compress the converted copies.