Combine Tools Into One Flow

Most photo jobs are not one conversion — they are three. The iPhone photo needs HEIC decoding, the location tag needs stripping before it goes public, the crop needs to be Instagram's 3:4 grid ratio (1080×1440 since the 2026 change), and the result needs to be under the platform's effective size ceiling. Doing that with four separate tabs means downloading and re-uploading between each step, or worse, sending the file to four different websites. The pipeline runs the whole chain in one tab: drop the files once, click Generate once, download the finished result.

The seven presets cover the chains people actually need. The original three are unchanged: “iPhone photo → Instagram post” is HEIC decode (plain JPGs pass through untouched) → EXIF/GPS strip → 3:4 grid resize with cover crop → compress to about 200 KB; “Compress for upload” is a bounded resize to 1600 px followed by a target-size compression — the right pair when a form rejects your file for being too big rather than too tall; “Photo → PDF” converts everything to JPEG q92 and combines the shots into one PDF, one page per photo, for portals that want a document rather than an image.

Two newer presets answer the carousel pain that ran r/Instagram all summer: once a video is added to a draft, Instagram locks the post to a single aspect ratio (the old edit-screen workaround died in 2026, and the thread chain from June to September confirms it is structural), so a carousel of mixed-ratio slides gets reshuffled at upload. “Photos → Instagram carousel (4:5)” normalizes every slide to 4:5 1080×1350 — the tallest shape the feed shows without cropping — with HEIC decode, EXIF strip, cover crop, and a q95 JPEG, so the whole carousel enters as one ratio. The timing is not casual: Instagram's Bonus program opened a photo/carousel track (US test, September 2026) that pays for photo and carousel views while Reels views do not count, which turned consistent slide prep from tidiness into income. “Max-quality Instagram export” is the other half — strip metadata, keep full resolution, JPEG q95 — the cleanest input Instagram's re-encoder can receive when you cannot beat platform compression.

“One photo → every Meta ad ratio” exists because of a change on the buying side: Advantage+ is now the default for new campaigns, and Meta removed per-placement ratio replacement from the Ads Manager, so a single creative runs across every placement and gets auto-cropped to whatever each surface wants. The accepted community workaround is separate ad sets, each carrying one exact-ratio asset — and this preset builds those assets from one photo: HEIC decode, EXIF strip, then a fan-out to 1:1, 4:5, 9:16, and 1.91:1 (1080-wide, cover crop, JPEG q95), one correctly named file per ratio. The sizing case is straightforward: a June 2026 industry sizing guide puts three aspect ratios — 4:5, 9:16, and 1:1 — at roughly 90% of all ad delivery, and Meta's own holiday playbook reports 2.1× higher purchase intent when shoppers see three or more creative formats. Those are guide numbers, not ours — but they say the same thing the workaround does: one ratio is not enough anymore, and the Ads Manager's creative-diversity rating (live August 26) reads the same signal.

“One photo → both Instagram schools” answers a quieter fight: the guides genuinely disagree on 3:4 vs 4:5, and the resizer tools that recommend one size rarely say what the other surface does to it. Put plainly, choosing 1080×1440 or 1080×1350 is choosing which surface crops — the 3:4 file keeps the profile-grid tile whole but is taller than the 4:5 feed cap Meta Business Suite warns about, while the 4:5 file keeps the feed view whole but gets center-cropped to 3:4 in the tile, losing about 33 pixels per side at full size. The preset fans out to exactly those two ratios from one photo — HEIC decode (plain JPGs pass through), EXIF strip, cover crop, JPEG q95, one named file per ratio — so no upload school is locked out. The upload guidance is the honest hedge: post the 4:5 when the feed is the surface you are protecting, keep the 3:4 for the tile-safe upload.

The pipeline is a batch tool, not a one-file-at-a-time page. Drop a whole camera roll — twenty or thirty photos at once — and the same flow runs on every file, producing a download per photo per output step. The flow itself (which steps and which options — never the files) is remembered in your browser's local storage, so a repeat batch the next day is one click. There is no daily cap, no credits, and no account, because there is nothing to meter: every render happens in your browser. Many web resizers cap free use at a few images a day or put multi-format export behind a paid tier; the facts of this offer are simply that it is uncapped and local. The files download straight from the tab, ready to hand off to your phone for posting — AirDrop, drive, or message, nothing in between.

The order matters, and the picker enforces it. Each step declares what it consumes and what it produces — an image step can follow an image step, but nothing can follow the PDF combiner because no step accepts PDF input yet. Steps that cannot legally run next are disabled in the picker instead of failing at run time, so you cannot build a broken flow. Reorder with the arrows, remove with ✕, and every option (output format, size preset, target KB) stays editable per step.

Chaining is also where tool farms and this page part ways. A site with eighty-plus tools invites you to chain anything with anything, and the failure shows up at run time — a step that cannot read what the last step wrote. This catalog is deliberately small — seven steps — and each one declares what it consumes and what it produces, so the picker offers only the orders that work; a broken flow cannot be built. The steps are also current with the 2026 platform specs: Instagram's 3:4 grid ratio (1080×1440), the 4:5 carousel normalize, the one-photo→every-Meta-ad-ratio fan-out, and the safe-zone-aware crop all live here as chainable steps, not as eighty separate pages you have to sequence yourself.

When a single tool is enough, use the single page. One plain JPG that only needs EXIF removal is faster on the EXIF remover; a webp that needs one format conversion does not need a pipeline. The pipeline earns its keep the moment the job has two or more steps — or when you will repeat the same job on the next batch: your flow (which steps, which options — never your files) is remembered in your browser's local storage, so the next visit starts where you left off.

Custom flows are first-class, not a hidden power feature. Start from any preset, delete the steps you do not want, and add others in any order the type system allows — for example HEIC decode → convert to PNG for a lossless still, or convert → strip → compress for a clean web upload with no resize. Every combination the picker permits will run, because each step is the same engine the single-tool page uses, wrapped to hand its output to the next step in memory.

Privacy holds for the whole chain, not each step separately. Files are decoded, transformed, and re-encoded inside your browser tab and exist only in memory between steps — they are never written to a server, never queued, and never persisted; the only thing saved between visits is the step list. That matters most exactly here, because the chain is usually fed with personal photos: the HEICs from a phone camera roll carry GPS coordinates, and the whole point of running HEIC → EXIF strip → resize → compress as one local flow is that the un-stripped original never leaves the device at all.