File converter presets for Mac: Yuzu image chains

Short answer

File converter presets for Mac let you reuse the same settings. A Yuzu Drag preset saves one configured operation or a compatible image chain. Chains run one to eight image transforms in order and publish only the final images; they cannot combine arbitrary file actions.

This page is the reference for names, editing, availability, destinations, and automation. For choosing a practical resize-and-compress recipe, use the batch image workflow guide.

Try a built-in reusable workflow first

Apple Shortcuts can save a repeated image-processing workflow without Yuzu. Add the built-in actions for the task, pass files between them, and give the shortcut an explicit save step. This is a reasonable choice when the whole job already lives in Shortcuts.

Preview also retains some export choices during normal use, but repeating a remembered choice is different from maintaining a named multi-step recipe. If you work occasionally on one image, repeating the export may be simpler than maintaining a preset library.

Yuzu presets are useful when the reusable configuration belongs to the same app you use for drag processing. A preset gives that configuration a name, and a compatible saved local transform can also be selected from Run Preset in Shortcuts.

Names and saved configuration

A preset name must contain one through forty characters after surrounding whitespace is removed. Use a name that describes the intended result or audience. A name such as Site images can be useful if you also keep the actual settings visible in its summary; the name alone should not be your only record of what the job does.

Open Presets to see saved items and their summaries. New Preset lets you choose an operation and configure it. The save editor includes the name, the configuration summary, and Save Preset. Edit Options… lets you revisit a single operation's options where available.

The list offers Edit…, Copy, and Delete. Copy creates another saved preset; it is not an instruction to duplicate the source files you will process later. Give copied presets distinct, descriptive names if you intend to maintain different configurations.

Deleting a preset removes that saved recipe and its wheel references. If a shortcut still refers to a deleted preset, select an existing compatible preset again in Shortcuts rather than assuming a new item with the same name has the old identity.

Build and edit a chain

Start with a saved eligible image transform, then use Edit… to open the chain editor. Its heading is Preset Chain. The editor shows the ordered steps, an Add Step menu, an Options control for each step, movement controls, and a removal control.

1. Give the preset a clear name within the forty-character limit.
2. Review the initial image transform and its options.
3. Use Add Step to add a compatible next transform.
4. Use Options to configure that step.
5. Arrange the order with the step movement controls.
6. Choose a Destination policy.
7. Save Preset only when the editor reports a compatible configuration.

The editor supports one through eight image transforms. It restricts the available choices to operations that can produce files, run without interaction, and support chaining. A valid individual operation is not automatically eligible for a multi-step chain.

Order matters. Each step must accept what the previous step produces. Resize followed by compression is a common example, but the right settings depend on the intended image use. Adding a step does not establish that its input and output requirements match the rest of the recipe.

Only final images are published. Do not depend on the intermediate result between two steps appearing beside the original. If you need an intermediate file for review, run the relevant operation separately and inspect it as its own job.

Destination policies and access

The chain editor's Destination menu includes Use Output Preferences, saved destinations, and Choose Folder…. Decide whether a recipe should follow your current app preferences or consistently target a specific authorized folder.

A saved destination is a reference to a folder, not a promise that the folder is currently available. The Presets window includes a Folders section with Reconnect… and Remove controls. Reconnect a moved or unavailable folder deliberately, checking its actual path before saving the recipe again.

The editor can require a valid saved destination before saving a chain. An automated run cannot repair that situation by opening a destination picker. If the destination is on a disconnected volume, reconnect the volume and review access before launching the batch.

Wheel availability and manual use

A saved preset does not appear for an arbitrary selection simply because it exists. Wheel availability depends on the group, pinning or customization, compatible inputs, and valid destinations. If a preset is absent, inspect those conditions before changing the recipe's processing settings.

For manual processing, begin dragging the images. Tap ⇧ for Convert or ⌘ for Tools; another ⌘ tap opens Actions. Release over the intended available wedge. A resize or compression preset belongs with its processing workflow, not an imagined extra modifier key.

Use a small initial selection and inspect the output's dimensions and appearance. A preset stores choices, not a promised file size or a judgment that those choices suit every image. Keep the originals so you can adjust the recipe and create another result if needed.

Automation and limits

Run Preset in Shortcuts supports compatible saved local transforms and image chains. It takes explicit Files input and returns output files. Configurations requiring interaction, sharing, mutation, or clipboard access are excluded. See the Shortcuts reference for setup and returned-file handling.

The image tools hub describes the underlying processing tasks. Keep this reference separate from your image-quality decisions: a technically valid chain can still be unsuitable for a particular delivery requirement. Test the actual recipe with representative files before making it part of a recurring handoff.

Related links

• Browse the tools hub
• Automation and reference documentation
• Download Yuzu Drag