About Toolcore

What you'll find here

Everything below mirrors the home catalog. Broad groups include Media, JSON, Calculators, and Data & text (encoding, crypto, compress, regex, identifiers, and AI-assisted helpers where useful).

When you sign in, you can pin a small set of tools on the home page for expandable inline panels (the same UI clients as the full-page tools). The catalog also gives automations a clear public URL to open when a workflow needs to hand off a small task.

• Media — Image convert: convert WebP, JPEG, and PNG; enhance tone and sharpness; resize; read EXIF and export without embedded metadata (tabs on one page); Image resize for max width/height with aspect ratio preserved. For suggested HTML alt text from an upload, see image → alt text (AI-assisted where available) or screenshot → steps for UI walkthroughs. QR code generator: Wi‑Fi/vCard builders, templates, PNG or SVG, optional logo and colors, locally; linear barcode generator (CODE128, EAN-13, UPC-A, ITF, PNG/SVG); GS1 GTIN checksum checker for pasted GTIN‑8 / UPC‑A / EAN‑13 / GTIN‑14 digit strings without catalog lookups. PDF tools: browser merge (more routes on the hub); Color tools: CSS color converter (HEX, RGB, HSL, OKLCH, named colors, harmonic relatives), harmony palette (complementary, triadic, and related sets), tint/shade scale (sRGB ramps and :root tokens), WCAG contrast, accessible color suggest for one fixed text or surface color, Tailwind-style theme for a primary ramp and light/dark CSS variables, MUI theme palette for createTheme snippets, HeroUI-style OKLCH theme variables for Tailwind v4 + @heroui/styles, and the 216 web-safe swatches with copy-as-HEX/RGB/RGBA.
• JSON — the JSON hub bundles: JSON formatter and validate (pretty-print, minify, escape, download); RFC 8259 syntax rules and checker; string and Unicode helpers; side-by-side compare; JSON ↔ XML; plist XML ↔ JSON; YAML ↔ JSON; JSON ↔ KDL; JSON ↔ MessagePack / CBOR; JSON ↔ BSON; TOML ↔ JSON; INI ↔ JSON; HOCON ↔ JSON; CSV ↔ JSON; Excel (XLSX) → JSON; JSON → Excel (XLSX); NDJSON / JSON Lines; JSON array chunks; JSON sort keys; JSON canonicalization (JCS); JSON → C# classes; JSON → Java classes; JSON → TypeScript interfaces; JSON → Zod schemas; JSON → Valibot schemas; JSON → TypeBox schemas; JSON → Python TypedDict; JSON → Rust structs; JSON Schema validate; JSON Schema $ref expand; JSON Schema multi-file bundle; JSON Schema → sample JSON; JSON Pointer & Patch; JSON5 / JSONC → JSON; JSON repair; JSON Merge Patch; JSONPath & JMESPath; jq filter; JSONata; JSON Logic; flatten / unflatten; extract JSON from text; pick or omit top-level keys; JSON ↔ Properties; JSON ↔ HTML table; JSON ↔ Markdown table; JSON → SQL INSERT; JSON → SQL CREATE TABLE; big integers; Base64 in JSON; JSON → curl; JSON → OpenAPI; JSON → AsyncAPI; JSON → GraphQL SDL; JSON → Protocol Buffers; JSON → Apache Avro; JSON → Go; JSON → Kotlin; JSON → Swift; JSON → PHP; JSON → Ruby; JSON → Clojure; JSON → Elixir; JSON → Scala; JSON → Haskell; JSON → CUE; JSON → Nim; JSON → Dart.
• Calculators — the calculators hub groups US-style utilities: sales tax, percentages, age, discount, tip (split check), loan payment (APR), compound interest (APY), profit margin, date difference, Roman numerals, a units tools hub for data sizes, length/temperature/weight, speed, volume, area, and pressure conversion, and unit converter (length, temperature, weight), speed converter (km/h, mph, knots), volume converter (L, US/UK gallons, cups), area converter (sq ft, acres, ha), pressure converter (bar, psi, atm) — all run in the browser unless a page states otherwise.
• Encoding & data
  • Data URL — inline Base64 snippets for images and small payloads.
  • Encoding tools (hub) — index of encoding-related routes (data URLs, hex, JWT, JSON helpers, and more).
  • Base64 & URL encoder — UTF-8 Base64 and URL component encode/decode in one workspace (encodeURIComponent / decodeURIComponent).
  • Base64url — RFC 4648 URL-safe Base64 ( -, _ ) for UTF-8; padding optional on decode (JWT segments).
  • URI percent-encoding — encodeURI / decodeURI vs encodeURIComponent for full strings vs components.
  • Punycode / IDN — Unicode domain labels ↔ ASCII Punycode (xn--) for DNS wire format.
  • Base32 (RFC 4648) — UTF-8 text ↔ standard Base32 alphabet for configs and test vectors.
  • Crockford Base32 — no = padding; alphabet omits I, L, O, U; decode maps O→0 and I/L→1.
  • LEB128 (ULEB + SLEB) — little-endian base-128 for wasm-style integers and varint-like streams (unsigned vs signed decodes in the same workspace).
  • ASCII85 (Adobe / PDF) — PostScript and PDF stream-style Base85 (five printable chars in !–u per four bytes, optional z for four nulls).
  • Z85 (ZeroMQ) — RFC 32 4→5 printable encoding; different alphabet from Adobe ASCII85 (see spec test vector HelloWorld).
  • Quoted-printable — MIME =XX escapes and soft line breaks for UTF-8 text parts.
  • Base58 — Bitcoin-style alphabet (no 0/O/I/l); UTF-8 bytes, not Base58Check.
  • Base-36 — 0-9a-z for UTF-8 bytes as one big-endian integer; leading 0x00 → leading 0.
  • Bencode (BitTorrent) — JSON ↔ bencode: strings, i…e integers, lists, byte-sorted dicts; output as hex.
  • Morse code — international (ITU-style) ./- for Latin, digits, punctuation; / between word groups in code.
  • Unicode & JS escapes — \u{…}, \uXXXX, \xNN encode/decode.
  • Compress & minify — minify HTML, JS, CSS, XML, SQL, JSON; batch image compression to JPEG or WebP.
  • Crypto — ciphers, digests, and Base64 in the browser.
  • HMAC — SHA-256/384/512/1, hex or Base64.
  • File checksum — SHA and CRC on local files.
  • CRC-32 & CRC-32C — IEEE and Castagnoli on UTF-8 text or hex bytes in the browser.
  • Subresource Integrity (SRI) — integrity tokens (SHA-256/384/512 base64) for scripts and stylesheets.
  • Luhn (mod 10) — checksum for digit strings (e.g. test PANs) in the browser.
  • IMEI & IMEISV checker — 15-digit IMEI breakdown with Luhn, 14-digit check digit hint, 16-digit IMEISV segmentation; no GSMA/carrier lookup.
  • VIN check digit — 1981+ North American-style 17-character vehicle IDs: ninth-position mod 11, WMI/year/plant field split locally; no DMV decode call.
  • ICCID checker — SIM/eSIM ICCID digits: E.118-style MII hint plus ISO/IEC 7812 Luhn on the pasted string locally; no HLR/carrier lookup.
  • NPI check digit — US National Provider Identifier: CMS Luhn on 80840 + 10 digits; no registry lookup.
  • IBAN validate — MOD-97-10 and length (embedded registry); no bank API.
  • BIC / SWIFT validate — ISO 9362 structure (8 or 11 characters); split fields only; no SWIFT directory.
  • ABA routing checker — MICR checksum for nine-digit Fed routing numbers; coarse Reserve district hint.
  • ISBN validate — ISBN-10 / ISBN-13 checksums and 978↔ISBN-10 conversion; no catalog lookup.
  • ISIN validate — ISO 6166 securities identifiers (12 characters, Luhn on expanded digits); no market data.
  • OAuth PKCE — code_verifier and S256 code_challenge in the browser.
  • TOTP / authenticator — RFC 6238 codes and otpauth:// enrollment locally.
  • PEM / X.509 viewer — inspect certificates locally.
• Text & data
  • Hex encode/decode for raw bytes.
  • HTML entity encode/decode.
  • Plain text diff.
  • Remove duplicate lines — keep first occurrences; optional trim, case-fold, or sorted output.
  • Sort lines alphabetically — locale-aware A→Z / Z→A or reverse order.
  • Word & character count.
  • Lorem ipsum.
  • Random string generator.
  • Password generator.
  • Bcrypt hash & verify — password digests with adjustable cost in the browser.
  • Markdown preview.
  • String case converter.
  • URL slug generator.
  • SQL formatter.
• Networking & time
  • Cron helper.
  • World clock (two zones).
  • IPv4 & IPv6 CIDR calculator.
  • MAC / EUI formatter — normalize layer-2 hardware addresses (colon, hyphen, dotted, plain hex) with multicast / local-admin flags; not IP routing.
  • Unix timestamp converter — epoch seconds or milliseconds, ISO-8601, UTC and local display.
  • ISO-8601 duration — parse P…/PT… or build normalized strings locally.
  • UUID / GUID generator (random v4, batch copy).
  • ULID generator.
  • MongoDB ObjectId — parse 24 hex or generate BSON-shaped ids locally.
  • Nano ID generator — URL-safe tokens, adjustable length and batch count (browser-only).
  • User-Agent parser.
  • Data size units.
• Reference tables
  • HTTP status codes.
  • HTTP methods.
  • HTTP headers.
  • MIME types & file extensions.
  • Common TCP & UDP ports.
  • SemVer compare & sort.
• Developer utilities
  • JWT decode — inspect header and payload locally (signature not verified; handle secrets carefully).
  • Regex generator & tester.
  • E.164 phone normalize — strip formatting and check international shape locally.
  • Open Graph preview.
  • robots.txt & sitemap preview.
  • Pseudo-CLI — terminal-style open + catalog id, optional -q prefill.
• Fun
  • Tarot spread.
  • Zodiac snapshot.
  • MBTI-style quiz (entertainment only).
• AI-assisted tools — the AI tools hub: natural language to regex, regex pattern explainer, JSON & error explainer, commit message from diff, diff review helper, explain shell (bash & sh), curl & HTTP request explainer, SQL query explainer, log snippet summary, stack trace explainer, environment lines explainer, tone rewriter, title & meta drafts, bullet expander, technical translator, image → alt text, screenshot → steps, CI/CD YAML explainer, pre-commit config explainer, Kubernetes YAML explainer, Helm chart explainer, Dockerfile explainer, Nginx configuration explainer, Terraform / HCL explainer, systemd unit explainer, Prometheus rules explainer, Ansible playbook explainer, Grafana dashboard JSON explainer, Docker Compose YAML explainer, Makefile explainer, OpenAPI explainer, test ideas from code, README & CHANGELOG drafts, LLM token estimate, character budget from token cap, UTF-8 byte size check, LLM context split & budget, long text chunker for chat paste, RAG chunk calculator, paste redact for AI, paste secret scan, prompt structure checklist, instruction & rule draft check, LLM output compare, AI & ML terms glossary (from token estimate through the glossary, browser-only; server-side AI-assisted help for the rest). Use the Regex tester for patterns; redact secrets before pasting into AI helpers.

Compared with typical tool sites

Plenty of one-off utility pages are genuinely helpful. Toolcore is built for people who bounce between many small tasks and want a single place that stays consistent—without pretending we invented JSON formatting or QR codes. The table below summarizes common differences at a glance.

We are not trying to replace every specialized service; we aim to be a dependable default when you need something solid, fast, and easy to return to.

For assistants and automation

Read the overview first: AI agents and automation. Toolcore exposes a machine-readable list of tools and URL query conventions for opening a page with prefilled text (many transforms run in the browser unless a page says otherwise). See /agent-tools.json for the manifest; /mcp-tools.json lists the same contract without AI-assisted entries. Use q / qb (Base64 UTF-8) on tools that accept a primary payload, or the per-tool keys described there (for example, JSON compare uses left / right). The manifest includes an integration block (URL manifest pattern) and a plain-English llmSystemPrompt; the same full-catalog prompt as plain text is at /llm-prompt.txt for easy copy-paste into assistant settings.

Browser pseudo-CLI and token use

The pseudo-CLI is a browser-only terminal-style UI: it navigates to catalog tools and can pass optional query prefill (e.g. -q), not a remote shell. For assistants, that matters in the same way as any other prefilled tool URL from the manifest: if the user runs the transform in the page, you can often return a short link or command instead of emitting the full formatted or encoded result in the chat. That typically reduces output length (and thus billed tokens on providers that charge by generated text) and avoids duplicating work the site already does locally. It is not unique to the CLI—a direct path?q= URL is often equally compact; the CLI is one way to express "open this tool with this input." For trivial outputs, the difference may be negligible; for large payloads or multi-step formatting, the gap is usually clearer.