Workflows

Step-by-step recipes that chain InstantTools together for one real job.

Each workflow takes one task, like sending a rental application or posting a product photo, and walks through the tools in the order that works, with the settings to use. Your files stay on your device the whole time.

For Social Media Managers

Social Media Asset Bundle

Turn one photo into correctly sized JPGs for Instagram and X, plus a lighter WebP copy for your own site.

Outcome: A 1080 × 1080 or 1080 × 1350 JPG for Instagram, a 1600 × 900 JPG for X, and a WebP copy for your website.

Recipe Steps (4)

1
Crop to the platform’s shape
Pick 1:1 for an Instagram square or 16:9 for X. Instagram portrait is 4:5 and has no preset, so choose Free and drag until the size readout’s height is 1.25 times its width (540 × 675, for example). The crop downloads as a full-resolution PNG.
2
Resize to exact pixels
Type 1080 as the width and leave “Maintain aspect ratio” on. A 1:1 crop becomes 1080 × 1080 and a 4:5 crop becomes 1080 × 1350. For X, type 1600 to get 1600 × 900.
3
Convert to JPG
Set the Image Converter target to JPG and drop in the resized PNG. It saves at quality 0.92 and fills any transparent areas with white. This is the file you post.
4
Make a WebP copy
Switch the target to WebP. The converter re-encodes the PNG you dropped in, not the JPG, so the copy doesn’t carry two rounds of compression. WebP is usually smaller than JPG at the same quality, so use it on your blog or shop page.

Start Recipe →

For Renters, applicants & freelancers

Secure Document Prep

Strip, redact, stamp, and shrink a sensitive document before you email it — without uploading it anywhere.

Outcome: A copy with no hidden metadata, nothing they don’t need, a stamp naming its purpose, and a size email accepts.

Recipe Steps (3)

1
Black out what they don’t need
Search for account numbers, your address, and other people’s names, and let the detectors catch emails, phone numbers, US Social Security numbers, card numbers, and IBANs. Redacted pages are rebuilt so the text is gone, not covered.
2
Stamp ID copies with their purpose
A passport scan that says “For Acme Lettings, 12 Elm St only · Oct 2026” is hard to pass off for anything else. The stamp repeats across the page at 32% opacity by default, so your details stay readable underneath.
3
Or do it all in one pass
Prepare a Document to Send removes hidden details, redacts, stamps, and compresses together, then re-checks the finished file before you download it. Removing hidden details is always on. Redaction and compression start on, and the stamp starts off.

Start Recipe →

For Developers

Developer Debug Bundle

Decode a JWT, format an API response, and read a Base64 header without pasting any of it into someone else’s server.

Outcome: A readable JWT payload with its expiry, a formatted JSON response, and a decoded auth header. All decoded on your machine.

Recipe Steps (3)

1
Decode the token
Paste the token from the Authorization header. A leading “Bearer ” is fine; the decoder drops it. You get the header, the payload, and, if the token has an exp claim, a line saying when it expired or will expire. The signature is not checked.
2
Format the API response
Paste the response body and press Format. It comes back indented with two spaces. If the JSON is broken, you get the line and column where parsing stopped.
3
Decode auth headers
Paste the value after “Basic ” and press Decode to see the username:password pair it carries. Works on any standard Base64 header or cookie value.

Start Recipe →

For Developers & Content Writers

Web Snippet Builder

Turn Markdown into a Base64-encoded HTML data URI ready to drop into any iframe or CMS field.

Outcome: A data:text/html;charset=utf-8;base64,… URI from your Markdown source.

Recipe Steps (3)

1
Write Markdown
Paste your Markdown into the input. It’s converted to HTML with GitHub-flavored Markdown on, so tables, strikethrough, and fenced code blocks work. Raw HTML in your Markdown passes straight through.
2
Minify HTML
Comments are removed, runs of whitespace collapse to a single space, and the gaps around block tags like <p>, <ul>, and <h2> are dropped.
3
Base64 Encode
The minified HTML is encoded as UTF-8 bytes, converted to Base64, and prefixed with data:text/html;charset=utf-8;base64, so it’s ready to paste and every browser reads the text as UTF-8.

Start Recipe →

For Designers & Photographers

Image Pipeline

Strip the metadata from a batch of photos and shrink them for the web in one run.

Outcome: Metadata-free images with the long edge capped at 2200 pixels, downloaded together as one ZIP.

Recipe Steps (2)

1
Strip metadata
JPEG and PNG files have their metadata blocks cut out without touching a pixel. GPS coordinates, capture time, camera model, and every other EXIF, IPTC, and XMP field are removed. Other formats, like WebP, are re-encoded once as high-quality WebP, which drops the metadata with them.
2
Compress
Each image is scaled so its long edge is at most 2200 pixels, then saved in its own format: JPEG and WebP at quality 0.78, PNG losslessly. If a file comes out bigger than it went in, the cleaned version from step 1 is kept instead.

Start Recipe →

For Content Marketers & SEO Specialists

SEO Boost

Extract keywords, generate a meta description, and build JSON-LD schema from any piece of content.

Outcome: A keyword list, a ≤155-character meta description, and a ready-to-paste Article schema block.

Recipe Steps (3)

1
Extract Keywords
Identify the highest-signal terms in your content using TF-IDF analysis.
2
Generate Meta Description
Summarize the content into a ≤155-character SEO description.
3
Build Schema
Generate JSON-LD Article schema from the extracted metadata.

Start Recipe →

For E-commerce Managers & Product Owners

Product Listing

Turn a feature list into a polished product description with keywords and structured data.

Outcome: Marketing copy, extracted keywords, and Product schema ready for your listing page.

Recipe Steps (3)

1
Generate Description
Transform your feature list into persuasive marketing copy.
2
Extract Keywords
Pull out the strongest search terms from the generated copy.
3
Build Schema
Generate JSON-LD Product schema for rich search results.

Start Recipe →

For Content Writers & Editors

Content Rewrite

Rewrite content for freshness, summarize for a different audience, and extract updated keywords.

Outcome: A rewritten version of your content, a concise summary, and an updated keyword list.

Recipe Steps (3)

1
Rewrite Content
Paraphrase the original text while preserving meaning.
2
Summarize
Generate a 2–4 sentence summary of the rewritten content.
3
Extract Keywords
Identify the core terms from the rewritten version.

Start Recipe →

How workflows work

A single tool does one thing. Most real jobs need three or four of them in the right order. Posting one product photo to Instagram and X means cropping, resizing, and converting. Emailing a bank statement to a landlord means redacting, stripping hidden details, and shrinking the file. A workflow writes that sequence down once, with the settings, so you don’t have to work it out each time.

Recipes and runnable pipelines

Some workflows are recipes. You open each tool in turn, and the page tells you what to set, why each step comes where it does, and what goes wrong if you skip one. Recipes suit jobs where you need to look at the result before moving on, like checking that a redaction caught every account number.

Others are pipelines. You drop in your files or paste your text once, press Run all, and each step feeds the next. The Image Pipeline and Web Snippet Builder work this way. Every step keeps its output, so you can open it to compare file sizes or grab an in-between version before the last step.

Your files stay on your device

The file tools in these workflows run inside your browser tab. Images are redrawn on a canvas, PDFs are opened and rebuilt by code in the page, and the finished file is created on your machine. Nothing is uploaded to a server to do the work. You can check this yourself: open your browser’s developer tools, switch to the Network tab, and run a file workflow. No request carries your file.

Each workflow page also lists the limits plainly: which formats a step accepts, what gets re-encoded, and where you’ll still need to check the result by eye.