The system of record for how work actually happens.
Drop a folder, build a recipe chain, and ship a packed zip. Bulk optimize applies one profile across mixed inputs; asset packs generate every published size from a single source; recipes chain resize, crop, compress, convert, and metadata-strip in any order.
Bulk optimize, asset packs, and chained recipes in a single queue.
FyDark Batch ships three named recipes — Web Ready, Social Post, Private Share — each a tuned chain of studio operations. Compose your own; save it locally; replay across single mode and batch alike.
Recipes are ordered chains of operations — resize → smart crop → compress → strip EXIF → convert. Drop a recipe on a queue and the runner applies the full chain to every file. Save tuned recipes for next time.
Pick a pack and the runner generates every output the destination expects — App Store sizes, OG card, X / LinkedIn, favicon set — radiating out from a single source in one click.
Compose a set of sizes + formats once; replay against any source.
Pick a pack — Indie Launch, Work Share, App Store, Social — and the engine generates every size the destination expects. One source fans out to favicons, OG cards, store screenshots, and platform-native thumbnails in one zip.
Six worker lanes process files concurrently, each through a five-stage pipeline. The playhead sweeps the timeline so you can see exactly where every file is in its run.
Drag a folder in or paste from the clipboard. The runner reads every file's format and dimensions before you set a single option.
Pick a built-in recipe or compose your own from the 8 studio operations. Drag-and-drop the order; each station shows its inputs and outputs.
Run the queue. The progress strip shows per-file savings as files complete; when the last file lands, the runner builds a single zip and downloads it straight to disk.
FyDark Batch ships for designers, developers, marketers, photographers, founders, and content creators — each as a workshop bay with their tools hung on numbered pegs.
Pick the Indie Launch pack on a master hero render and ship favicon set, App Store screenshots, OG card, and social tiles in one zip. All sized correctly, named by destination, every file under platform caps.
Drop the marketing hero folder, set a single profile (WebP at q.86, max 1920px wide), and walk away with a deploy-ready zip. Every image converts, resizes, and compresses in one pass.
One master hero composes into a saved Social Post recipe — Instagram square + portrait + story + reels + X + LinkedIn cards, every variant sized correctly, every file named by platform.
Drop a 200-image shoot folder, apply a Cinematic + WebP at q.92 + strip EXIF recipe, walk away with a clean zip. Faster than firing up a desktop tool when the only goal is web export.
Indie Launch pack covers App Store screenshots, Play store covers, Microsoft Store images, Open Graph, Product Hunt, Twitter / X cards, LinkedIn covers, and favicons in one chain. Saved as a recipe for the next launch.
Set a target byte budget per format and bulk-optimize a content batch through the chain. Every file lands inside the platform's upload cap; rejection bounces drop to zero.
Each FAQ is a numbered step with a figure reference, a hand-checked margin note, and a §6.x section anchor. Read in order or skip to the figure that matters.
Read in order or skip to the figure that matters. Each step references a named diagram from elsewhere in this binder; margin notes are the shorthand version for repeat operators.
Practical ceiling on a typical laptop is around 200–400 images depending on size and target format. The bottleneck is RAM more than CPU — large source images held in memory parallel can hit limits. The runner streams workers and clears intermediate buffers between stages, so you can chain through long queues without memory blow-up.
Memory is the bottleneck, not CPU.
Bulk optimize is a single-step shortcut: apply one quality + format profile across every input. A recipe is a multi-step chain — resize, then crop, then compress, then strip EXIF, then convert — applied in order. Use bulk optimize when you need a one-knob solution; use a recipe when the job needs sequencing.
Bulk = single step · recipe = chain.
Yes. Compose any chain of operations, tune the parameters, and save it locally with a name. Saved recipes appear in the recipe shelf alongside the three built-ins. Recipes are stored in browser local storage — no account, no cloud sync, no per-device limit.
Recipes live in localStorage.
Parallel where the hardware allows. The runner uses Web Workers up to `navigator.hardwareConcurrency` (typically 4–12 on modern laptops). Files in the queue process in parallel up to that limit; each file's internal stages run sequentially within its worker.
Workers = navigator.hardwareConcurrency.
Yes. The queue control bar exposes pause, resume, and cancel. Pausing keeps already-completed files in the output buffer; resuming picks up at the next pending file. Cancelling discards in-flight encodes but preserves anything already finished.
Pause keeps progress.
No. Bulk optimize, asset packs, and recipes all run entirely on the Canvas API in your tab — same engine the single-image flows use. Source bytes stay on-device, intermediate buffers stay in memory, and the final zip downloads directly to your disk. Refresh the page and the queue clears.
Refresh clears the queue.
Every track on this page links to its own dedicated workspace — resize, crop, compress, convert, effects, batch, SVG cleanup, privacy. Same canvas, same recipe shelf, more depth where you need it.