Loading…
The Recipe Builder lets you string several conversion steps into a single chain and run them in one click, instead of opening one tool, downloading the result, and feeding it into the next by hand. You assemble a recipe from ingredient blocks — each step passes its output straight to the step after it — which makes ByteShift a batch file converter online that can convert multiple files at once free, automating conversion across a whole folder in one pass. Like every other studio, a recipe runs entirely in your browser, so the speed and privacy of a single conversion carry over to the full chain.
A recipe is built from blocks. Each one wraps a tool you already know from the studios, and the builder only lets you connect blocks whose types line up — so a chain is valid before you run it. These are the blocks available right now.
Re-encodes every image in your batch to another format — PNG, JPEG, WebP, AVIF, GIF, or BMP. As the first step in a chain it turns the builder into a bulk image converter: drop fifty photos, pick a target format, and convert them all in one pass instead of one at a time in the Image studio.
Wraps each image in its own PDF page. On its own it is a quick way to turn a folder of scans or screenshots into PDFs. Its real power shows when you follow it with PDF Merge — see the example below — to fold a stack of images into a single document.
Rewrites the container and extension of each audio file — MP3, WAV, AAC, FLAC, or OGG — without re-encoding the audio. It is the batch equivalent of the Audio studio, useful for relabeling a set of tracks to the extension a player or upload form expects.
Does the same for video, switching between MP4, WebM, MKV, MOV, and AVI containers across a batch. Like the Video studio it rewrites the container rather than transcoding, so it is instant and lossless. (It does not extract or separate the audio track — it works on the whole file.)
Shrinks each PDF in the batch, with a low, medium, or high strength setting. Chain it after Image → PDF, or run it on its own to get a folder of documents under an email or upload size limit.
These are the two finishing blocks, and each combines everything into a single download. PDF Merge concatenates all the PDFs in the chain into one document, in order. Package to ZIP bundles whatever files the chain has produced — images, PDFs, audio, or video — into one ZIP archive. Because both collapse many files into one, they can only sit at the end of a recipe.
Add Image → PDF, then PDF Merge, drop in a batch of images, and click Cook Recipe. Every photo becomes a page and the pages are merged into a single PDF — a job that would otherwise mean converting each image and then merging by hand. Swap the last block for Package to ZIP instead and you get every converted file in one archive.
The first reason is speed and convenience. A recipe collapses a multi-tool routine into one action: you set the chain up once and let it run over the whole batch, instead of shuttling files between studios, downloading and re-uploading intermediate results, and repeating the same clicks for every file. For a workflow you run often, that is the difference between a minute of fiddling and a single click. And because the steps run back to back in memory, there is no waiting on a server between them — the whole chain finishes about as fast as your machine can work through it.
Privacy is the second reason, and nothing about chaining steps changes it. A recipe runs on the same in-browser engines as the individual tools, so your files never leave your device at any point in the chain — not even between steps. There is no upload, no temporary copy on a server, and no retention policy to read through, whether you run one step or six. It is also genuinely approachable: you do not need to understand how the tools connect, because the builder blocks any combination that would not work.
The builder has a palette on the left and a mixing bowl in the middle.
Prefer to work one step at a time? Every block maps to a full studio — the Image, Video, Audio, and PDF tools each run the same conversions on their own.
A recipe is a chain of tool steps you assemble yourself. You add ingredient blocks into the Mixing Bowl, each step feeds its output into the next, and clicking Cook Recipe runs the whole chain over your files in one pass — all in your browser.
Yes — assembling your own chain is the only way recipes work. There are no fixed presets. You choose the blocks, set their options, and arrange the order, and the builder greys out any block that cannot accept the previous step’s output so your recipe is always valid before it runs.
Yes. A recipe uses the same in-browser engines as the individual studios. Nothing is uploaded — your files are read, processed step by step, and saved back to your device, so a multi-step recipe is just as local as a single conversion.