Workflow Guides
Choose the situation that matches your input and intended result. Each guide explains a concrete task, representative non-sensitive example, common failure modes, privacy or security boundaries, and the final check to perform in the system that will use the result.
PDF manipulation and conversion tools
Use this workflow when invoices, forms, reports, or scanned pages need to be combined without sending files through an account-based document service.
Open guideUse this workflow when only part of a PDF needs to be sent, archived, printed, or attached, and the source document should stay on your device while you verify the extracted copy.
Open guideUse a review-first page deletion workflow to keep an untouched source, select PDF positions accurately, rebuild a share copy, and check every boundary page in the downloaded result.
Open guideUse this workflow when several phone photos need to become a single PDF for reimbursement, records, school forms, support tickets, or document submission.
Open guideReview each PDF thumbnail, apply quarter-turns only where needed, use bulk rotation cautiously, and reopen the downloaded file so every page reads correctly in a separate viewer.
Open guideUse this workflow when a PDF needs a Draft, Confidential, Internal Use, or reviewer note before it is sent outside a team or uploaded to a portal.
Open guideUse this workflow when a PDF page needs to appear as an image in a report, presentation, support ticket, preview, or documentation screenshot.
Open guidePrepare mixed source documents as PDFs, remove and rotate problem pages, merge the reviewed files, and compare the final package with the destination requirements.
Open guideImage manipulation and editing tools
Encode and decode text in various formats
Use this repeatable workflow for encoded JSON fields, webhook metadata, headers, cookies, and logs. It validates the alphabet and padding before decoding, preserves binary bytes for download, and keeps Base64 separate from encryption or signature verification.
Open guideUse the local file mode and explicit checksum comparison to confirm byte equality before trusting a release archive, backup, or installer. A match does not certify the publisher or prove that the file is malware-free.
Open guideUse this workflow when data inside one query parameter contains spaces, ampersands, equals signs, Unicode, a plus sign, or another complete URL.
Open guideUse this workflow when a callback, webhook, proxy, SDK, or copied link contains `%252F`, `%2520`, `%253A`, or another sign that a percent sign was encoded again.
Open guideUse this workflow when a browser request, API response, redirect, or CDN cache behaves differently than expected and you need a bounded, redacted header-level record before editing configuration.
Open guideUse this workflow when an API, database field, DNS label, email body, configuration file, or legacy transport asks for Base32, Base58, Base62, Base85, hexadecimal, entities, Punycode, quoted-printable, UTF-16, or UUEncode but does not fully describe the variant.
Open guideUse this workflow when an internationalized hostname appears as readable Unicode in one place and xn-- ASCII labels in another, and you need a precise comparison without confusing conversion with registration or security approval.
Open guideUse the original file bytes to distinguish confirmed Unicode signatures from structural evidence and conservative heuristics. Then verify a candidate decoder against known headers and multilingual values before a full import.
Open guideCharacter-set detection narrows decoder candidates; it does not reverse already-corrupted text by itself. Preserve the source, identify where the wrong decode happened, compare controlled previews, and convert once only after known values round-trip correctly.
Open guideA reliable Unicode-normalization workflow preserves the original representation, confirms the target system's contract, distinguishes canonical normalization from compatibility folding, inspects exact code points and hidden characters, compares the result, and validates the completed value where it will be stored or matched.
Open guideThis workflow uses the Cipher Learning Workbench to make XOR byte mechanics visible. You will reproduce a known vector, switch between Hex and Base64, reverse it with the same key, and document why the exercise must never be presented as protection for real secrets.
Open guideFormat and beautify code and data
Use this workflow when a compact response is hard to inspect, a fixture fails strict parsing, or a generic client error must be traced to an exact JSON location without confusing syntax with API-contract validity.
Open guideA Markdown preview is most useful as a review stage, not as a promise that every destination will render the same document. This workflow keeps the working text in the browser, checks common extended syntax and sanitized raw HTML, treats remote images as an explicit privacy decision, and separates content markup from destination styling. It finishes by testing the exported HTML fragment or original Markdown in the system that will actually publish it.
Open guideHTML-to-JSX conversion removes repetitive syntax work, but migration quality depends on what happens afterward. This workflow records the original behavior, limits the conversion to one coherent fragment, compares browser-normalized structure, rewrites legacy events and URLs, moves styles and assets into the destination project, and finishes with lint, type, accessibility, responsive, and security checks. The generated JSX is treated as reviewable source, not as a sanitized or complete component.
Open guideHTML-to-Markdown conversion can remove repetitive rewriting, but a publishable migration also needs content isolation, trust-boundary review, asset relocation, and a real destination preview. This workflow converts one article or documentation section, checks every removed or preserved structure, replaces unsafe links and interactive controls, moves images, and verifies the finished file with the renderer that will actually publish it.
Open guideHTML-to-Pug conversion removes repetitive tag rewriting, but a dependable migration also needs a source baseline, dependency inventory, active-code redesign, explicit template locals, and tests in the destination application. This workflow converts one coherent view, checks browser normalization and preserved events or URLs, moves page dependencies, adds only the Pug logic the application needs, and verifies the compiled HTML rather than approving a file because its syntax parses.
Open guideFormatting and minification should produce reviewable, reproducible artifacts, not hide syntax errors or change data tokens. This workflow classifies the source and destination first, removes secrets, runs a language-specific parser, records exact settings and byte changes, compares semantic boundaries, and verifies the candidate in the real browser, compiler, loader, schema, and test suite before replacing the original.
Open guideSQL formatting can expose joins, predicates, grouping, and subqueries, but readable output is not evidence that a statement is valid or safe. This workflow identifies the target database and version, preserves and redacts the source, applies one explicit formatter grammar, reviews exact token and comment changes, and then verifies schema resolution, permissions, result sets, plans, transactions, migrations, tests, and rollback in the real toolchain.
Open guideUse this workflow when a response is valid JSON but too large to inspect manually, and you need a focused list of values for debugging, QA, or documentation. Keep the expression beside the extracted result so another person can repeat the selection against a newer response instead of relying on a one-time copy.
Open guideUse this workflow when a bug report, test failure, or production log includes a large JSON payload and you need to isolate request IDs, statuses, pagination links, or nested error fields.
Open guideConvert between different formats and units
Use this workflow when a spreadsheet export needs to become API-ready JSON, a fixture, or a reviewable dataset while preserving the text that the sheet actually contains.
Open guideUse this workflow when an API example, application config, or deployment manifest needs to move between JSON and YAML without silently changing a key or numeric value.
Open guideA documentation table is reliable only when its source shape, conversion rules, and published rendering agree. This workflow starts with a scrubbed representative fixture, distinguishes quoted CSV from strict JSON object arrays, protects large numbers and nested values, checks every generated header and padded cell, and verifies the finished GFM with the exact renderer that will publish it.
Open guideUse this workflow when an API response, fixture, or exported JSON array needs to become a spreadsheet-friendly CSV table for review, sorting, filtering, or sharing.
Open guideUse this workflow to turn a representative API response into a useful TypeScript starting point without pretending that one payload is the complete contract. It combines strict JSON cleanup, several array samples, explicit inference review, compilation in the target project, and runtime validation at the network boundary.
Open guideRepresentative fixtures preserve the shape and constraints of production records without preserving real people, identifiers, or secrets. This workflow inventories a target schema, generates only bounded valid values, adds deliberate minimum, maximum, duplicate, empty, and malformed cases, validates the exported encoding in the real importer, and saves stable fixtures when tests must be reproducible.
Open guideUse this workflow when a spreadsheet export, API fixture, or CSV/JSON handoff fails because columns shift, headers disappear, characters look broken, or JSON will not parse.
Open guideUse this workflow to replace production identifiers with generated UUID v4 values while preserving each field's syntax and relationships. It covers schema mapping, browser-local batch generation, version and uniqueness checks, deterministic fixture storage, database constraints, and the security boundary between a record identifier and authorization.
Open guideUse this workflow when an OAuth, SSO, webhook, campaign, or application callback looks correct in a browser but the receiving system reads another path or parameter value.
Open guideUse this workflow when a callback, search link, webhook, or API request changes plus signs, repeated keys, JSON string escapes, or a nested return URL after more than one parser touches it.
Open guideUse this workflow when a query string is present but the receiving app reads the wrong value, loses a parameter, or treats encoded text as literal data. The goal is to identify the broken layer before rebuilding the link, not to repeatedly encode the entire URL until it appears to work.
Open guideUse this workflow to turn a small, redacted log or payload sample into reviewable timestamp rows while preserving field names, source lines, exact epoch precision, and explicit unit decisions.
Open guideUse this workflow after you have identified the timestamp fields and need to order cross-system events, separate event time from ingest time, account for clock skew, and explain the result without overstating causality.
Open guideUse this workflow to determine whether a request occurred before nbf, at or after exp, or inside the stated token window, while documenting clock-skew policy and removing the raw token from shared evidence.
Open guideText manipulation and analysis tools
A cron expression is not a complete schedule until its field dialect, IANA time zone, starting instant, DST behavior, and missed-run policy are known. This workflow first converts every reference date to an explicit ISO 8601 instant, then inspects a five-field Unix cron expression field by field, compares future runs in local wall time and UTC, exercises a daylight-saving transition, and verifies the same cases in the production scheduler before a job is enabled.
Open guideText cleanup is safest when it is treated as a sequence of explicit, reversible transformations. Preserve the source, identify line and delimiter boundaries, make one structural change at a time, promote only reviewed output to the next step, and compare the final text with the destination contract before publishing, importing, or sharing it.
Open guideA slug generator can produce a consistent path-segment candidate, but it cannot own the route or protect a published address. This workflow records the target platform and current URLs, chooses an explicit Unicode or ASCII convention, reviews transliteration and encoded length, checks duplicates and reserved names in the real namespace, and treats redirects, canonical metadata, internal references, sitemap updates, monitoring, and rollback as required parts of any live URL change.
Open guideUse this workflow when an editor, researcher, support team, or SEO review asks whether a draft repeats words, contains a target phrase too often, reads easily, sounds negative, or resembles another version. It records the unit, language, normalization, denominator, limits, and interpretation before analysis, then separates deterministic evidence from editorial judgment.
Open guideUse this workflow when a test, mockup, terminal demo, documentation example, or harmless visual experiment needs generated or rearranged text. It separates structural operations from decoration, preserves source and separator behavior, records every seed and limit, and requires a plain-text alternative whenever FIGlet, mirror, upside-down, Braille-subset, or Zalgo output may not survive fonts, assistive technology, search, or copying.
Open guideUse this workflow when code viewers, PDFs, transcripts, legal documents, or exported notes add numbers at the start of copied lines. Keep the source, distinguish marked numbering from ambiguous plain integers, compare cleanup evidence, and validate the result before reuse.
Open guideUse the explicit Plain gutter format when an IDE, PDF, or documentation viewer copied a leading integer before every stack-trace line. Compare the result with the raw trace, preserve diagnostic values, redact secrets, and only then share it.
Open guideA multiline regex review needs the original line structure, a known pattern representation, deliberate flags, exact match and capture ranges, and a failing near-match. Run the native expression in an isolated worker, interpret offsets as UTF-16, and verify the final pattern again in the destination runtime before replacement or deployment.
Open guideRegex escaping is layered. First identify the source representation, decode only that representation, write the intended raw pattern body, and test it against exact positive and negative text. Then encode the verified body once for the destination JavaScript, JSON, or configuration format instead of adding backslashes by trial and error.
Open guideUse this workflow for a plain list copied from a spreadsheet, report, log, or editor when every row needs the same label, marker, wrapper, or delimiter. It keeps line boundaries exact and separates bulk text insertion from JSON, CSV, SQL, shell, or HTML validation.
Open guideA reviewable workflow for cleaning empty and whitespace-only rows while preserving the structure, order, and line-ending details that still matter.
Open guideUse this workflow when two values look identical but compare, search, wrap, parse, or render differently. Map supported controls before editing, distinguish common hidden separators from joining and line-break controls, retain exact line endings and normalization, and record why each removal was safe.
Open guideUse this workflow when an invisible leading signature changes the first CSV header or script token. Work from the original bytes, distinguish UTF-32 LE from its UTF-16 LE prefix, and do not remove UTF-16 or UTF-32 byte-order evidence until the destination is known.
Open guideUse this incident workflow when a Windows-edited script fails on Linux, Git shows a whole-file line-ending diff, or generated text mixes CRLF and LF. Inspect first, normalize only confirmed text, then enforce the decision with repository settings.
Open guideA practical workflow for turning repeated one-item-per-line data into an auditable unique list while preserving the first useful occurrence.
Open guideA review-first workflow for producing a unique, naturally ordered list of IDs, names, URLs, tags, or labels without confusing sorting with normalization.
Open guideUse a case converter to draft names, then treat every rename as a contract change: inventory consumers, define acronym rules, review invalid identifiers, compare a diff, and verify the destination.
Open guideA useful diff workflow starts with exact input, not filters. Preserve the source files, compare line structure and final newlines, explain every raw addition and removal, use equivalence options only as a diagnostic view, and validate any exported patch against a disposable copy before it reaches a repository or deployment.
Open guideA safe bulk-replacement workflow starts with an untouched source and the narrowest matching rule. It proves patterns separately, makes every flag and dollar token explicit, reviews boundary and zero-width diagnostics, compares the exact output, and tests the destination instead of treating a replacement count as correctness.
Open guideA reliable text-limit check starts from the destination contract, preserves the source representation, measures several Unicode units, includes normalization and invisible-character fixtures, exercises the limit on both sides, and verifies the value after storage or transmission.
Open guideColor conversion and manipulation tools
QR code generation and scanning
Security and encryption tools
Use this workflow when a login, API request, or permission check fails and you need to inspect token claims before changing auth code.
Open guideA random generator solves only the value-selection step. A reliable password workflow begins with the real service contract, uses a trusted device and a unique long value, saves the result in a password manager before submission, verifies that the destination accepted the complete value, enables phishing-resistant authentication where possible, records recovery material separately, removes clipboard and downloaded plaintext, and retains enough evidence to recover or revoke access without reusing the secret.
Open guideA password meter can reject obvious patterns, but it cannot certify an account. This workflow limits testing to new or synthetic candidates, prepares a trusted browser environment, checks the complete value without silent trimming, interprets zxcvbn scores and guess orders as rough model output, treats NIST length checkpoints as verifier requirements, performs breach monitoring and service controls separately, and records only non-secret decisions. The outcome is either reject and regenerate, accept provisionally for one account, or escalate to the destination's security policy without ever placing the tested value in a ticket, screenshot, analytics field, or shared note.
Open guideUse this workflow to turn a curl -I or DevTools capture into repeatable release evidence. It checks the final response locally, separates enforced CSP from Report-Only monitoring, preserves deployment context, and ends with live verification plus the application checks that response headers cannot cover.
Open guideUse this workflow when a CSP blocks an expected resource, a candidate policy produces noisy reports, or a proxy changes the header you intended to ship. It combines local policy parsing with browser violation evidence and a final deployed-edge check, without treating static findings as a security certificate.
Open guideStart with the representation you have, the exact change you need, and the system that will consume the result. Preserve an untouched source and record any format, size, privacy, or compatibility rule before opening a tool. A technically valid result can still be wrong for its destination.
For JSON, CSV, YAML, SQL, URLs, and timestamps, decide which parser or importer is authoritative. Preserve identifiers, duplicate keys, number precision, quoting, time zones, and empty values instead of judging only by readable output.
For cleanup, case conversion, Unicode, Base64, and line-ending work, distinguish visible characters from code points, bytes, separators, and binary data. Compare a reversible operation with a round trip whenever the format allows it.
Decoded JWT claims, password estimates, hashes, CSP reviews, and response-header checks are diagnostic evidence, not authorization or a security guarantee. Confirm the final decision with the issuing service, deployed response, or approved security process.
For PDF and image work, keep the original, check page or image order, dimensions, orientation, transparency, readability, and output size, then reopen the downloaded file in a separate viewer before sharing it.
QR codes, markup, types, tables, fixtures, and formatted code should be tested with the scanner, compiler, renderer, schema, or importer that will actually use them. Treat browser output as a reviewable draft until that check passes.
The tool can confirm its own operation, but it cannot know every contract in the destination system. Use these checks before replacing a source, deploying code, sharing a file, or making a security decision.
Keep an untouched source and record the exact mode, options, format, and expected result so the operation can be repeated.
Compare values, order, counts, bytes, warnings, and boundary cases that matter to the task instead of checking appearance alone.
Open, parse, scan, compile, import, or validate the result with the actual destination before treating it as complete.
Remove secrets and personal data from examples and support requests, and keep important source material until the result is accepted.