Tool guides

Choose PNG or SVG, check fonts and scale, and keep code readable when you share a snippet.

Use presets or edit 3–32 polygon points for avatars, directional images and slanted cards; compare full CSS with a clip-path declaration.

Format first when reviewing unfamiliar code; minify only the version intended for delivery.

• Preserve sourceKeep an original copy before transforming source.
• Review semanticsTreat formatter output as a readability change, not semantic validation.
• Verify artifactsUse hash verification to compare artifacts; a hash cannot decrypt source material.

Choose dimensions, crop, and output format from the destination’s constraints rather than habit.

• Start with qualityResize once from the highest-quality source available.
• Check transparencyInspect transparency before converting SVG or PNG assets.
• Export explicitlyDownload the generated file before closing the tab; local workspaces do not keep a cloud copy.

The processing label is part of the tool contract and should be checked before entering data.

• Process locallyLocal-first runtimes process input in the active browser tab.
• Describe, don’t pasteFeedback forms accept descriptions only and explicitly exclude workspace contents.
• Clear shared devicesClear the workspace and downloaded files when using a shared computer.

The architecture guide maps both processing designs, shows how to verify a local claim with your own browser, and lists the documents that should never be uploaded.

Merge, split, rotate, organize, watermark, compress, convert, and clean PDF files inside the browser tab—each task links straight to its workspace.

Location coordinates, a device serial, and the exact second a photo was taken can travel inside the file—this guide shows how to read that hidden layer and strip it locally before sharing.

Crop first, resize once, and convert to the format the destination accepts—this guide turns a dimension or byte budget into an ordered local workflow.

Pretty-printing, tree inspection, and deterministic diffs—how to read an unfamiliar payload before approving it, and the exact limits of the local runtimes.

Email and portal caps are unforgiving—this guide measures first, weighs structure cleanup against strong raster compression, and sets honest expectations by content type.

What the encoding actually is, how to calculate its size overhead, where data URLs and email earn it, why it is not a security mechanism, and how to debug malformed strings.

HEX, RGB, and HSL describe sRGB colors in different ways. This guide covers alpha, HSL harmonies, CSS Color 4, and sampling decoded artwork pixels in the browser.

A write-test-refactor loop with realistic samples, catastrophic-backtracking hygiene, anchoring, and flag semantics—run inside a worker with a timeout, so runaway patterns cannot freeze the tab.

PNG, JPEG, WebP, and AVIF compared by content type, transparency, real-world support, re-encoding costs, and measured byte savings—so the choice is a decision, not a habit.

Five fields and their ranges, the day-of-month/day-of-week OR trap, Sunday as 0 or 7, and daylight-saving edge cases—validated against the next ten computed runs before deploy.

Physical size by scanning distance, the four-module quiet zone, error-correction levels and logo overlays, enforced contrast, and proof-scanning before the print run.

What the supported subset converts and what flattens, how sanitization and a link-scheme allowlist keep the output safe, what the round trip back to Markdown loses, and where conversion belongs in a docs or blog pipeline.

Integrity versus authenticity, why MD5 and SHA-1 are integrity-only today, a one-minute installer verification, and hashing sensitive text without uploading it.

Random v4 versus time-ordered v7, ULID’s sortable base32 layout, what random keys do to a B-tree index, collision math, and generating batches locally.

The DevTools network check, the canary-string technique, and the cache and service-worker caveats — plus the open evidence harness anyone can re-run against the live site, re-captured on a schedule.