About Toolcore
Toolcore is for developers and technical staff who want fast, dependable utilities in one place—formatting and comparing data, converting formats, encoding, hashing, working with media, and similar everyday work.
The default is in-browser processing so your input stays on your device unless a tool clearly needs the server. Where a route uses generative AI or other server-side logic, the page states it. Assistants and automation are secondary: the same catalog exposes manifests and URL prefill so workflows can open a tool with payload instead of redoing work in chat—see AI agents & LLM integration and the sections below.
What you'll find here
Everything below mirrors the home catalog. Broad groups: Media, JSON, Calculators, and Data & text (encoding, crypto, compress, regex, identifiers, and AI-assisted helpers where listed).
- Media — Image tools: 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
alttext from an upload, see image → alt text (AI-assisted when configured). QR code generator: Wi‑Fi/vCard builders, templates, PNG or SVG, optional logo and colors, locally. Color tools: CSS color converter (HEX, RGB, HSL, OKLCH, named colors, harmonic relatives), WCAG contrast for text vs surface, 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); string and Unicode helpers; side-by-side compare; JSON ↔ XML; YAML ↔ JSON; JSON ↔ MessagePack / CBOR; TOML ↔ JSON; CSV ↔ JSON; NDJSON / JSON Lines; JSON sort keys; JSON canonicalization (JCS); JSON → C# classes; JSON → Java classes; JSON → TypeScript interfaces; JSON → Python TypedDict; JSON → Rust structs; JSON Schema validate; JSON Pointer & Patch; JSON5 / JSONC → JSON; JSON Merge Patch; JSONPath & JMESPath; flatten / unflatten; JSON ↔ Properties; JSON ↔ HTML table; big integers; Base64 in JSON; JSON → curl; JSON → OpenAPI; JSON → Go; JSON → Kotlin; JSON → Swift; JSON → PHP; JSON → Ruby; 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, and unit converter (length, temperature, weight) — all run in the browser unless a page states otherwise.
- Encoding — Encoding tools (Base64 and URL on-page, plus a list of related tools); hex encode/decode for raw bytes; HTML entity encode/decode; data URL for inline Base64 snippets; file checksum for SHA and CRC on local files.
- Crypto — Ciphers, digests, and Base64 (e.g. AES, DES, RC4, Rabbit, TripleDES, MD5, SHA families) in the browser.
- Compress & minify — Minify HTML, JavaScript, CSS, XML, SQL, and JSON, plus batch image compression to JPEG or WebP locally.
- Regex — Presets (email, URL, phone styles), a JS snippet, and a local tester.
- Text & snippets — Plain text diff; Lorem ipsum; password generator, random string generator; data size units.
- Scheduling, networking & text — cron helper; world clock (two zones); IPv4 & IPv6 CIDR calculator; SQL formatter; string case converter; Markdown preview; User-Agent parser; HTTP status codes; MIME types & file extensions; SemVer compare & sort; HTTP methods; ULID generator; PEM / X.509 viewer; word & character count; Open Graph preview; robots.txt & sitemap preview.
- Pseudo-CLI — Terminal-style commands (e.g.
open+ a catalog id) to jump to tools with optional-qprefill; same client-side JS as the GUI. - AI — the AI tools hub: natural language to regex, JSON & error explainer, commit message from diff, shell command explainer, log snippet summary, tone rewriter, image → alt text (server-side generative AI when configured). Use the Regex tester for patterns; redact secrets before pasting into AI helpers.
- Time — Unix timestamp converter: epoch seconds or milliseconds, ISO-8601 parsing, UTC and local display.
- Identifiers & tokens — UUID / GUID generator (random v4, batch copy); JWT decode to inspect header and payload locally (signature not verified—handle secrets carefully).
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.
| Topic | Typical tool sites | Toolcore |
|---|---|---|
| Finding & grouping | Each search can land on a different domain or layout; related tasks (e.g. format vs compare JSON) are often split across unrelated pages. | One home catalog plus hubs such as JSON and Color so related utilities sit together. |
| Where your input runs | Often unclear whether text or files are processed only in the browser, sent to a server, or passed to a third party—details may be buried or generic. | Each tool explains what runs in your browser, on our servers, or via generative AI when configured, so you can decide what to paste and where (see per-page notes and execution labels). |
| Automation & assistants | Usually optimized for ad clicks and one-off visits; little or no shared contract for scripts, IDEs, or assistants to open a tool with prefilled input. | Public /agent-tools.json, /mcp-tools.json (non-AIGC subset), and documented URL query keys (q, qb, and tool-specific pairs) so the same pages can be opened with prefilled payloads when that fits your workflow. |
| Look & feel | Visual design, density, and ad placement vary widely between sites; you re-learn a new UI on every tab. | Shared layout, typography, and compact toolbars across tools so frequent switching is less jarring (specialty sites may still beat us on depth for a single niche). |
| Your shortcuts on the home page | Rarely any way to pin specific utilities to the site's own home screen; you rely on browser bookmarks or history, which are generic and not tied to that catalog. | With an optional account, you can choose a small set of catalog tools to surface as shortcuts on the home page (home tools settings)—so your usual flows stay one click away without managing a separate bookmark folder. You can also pin a few tools to expand inline on the home page (below the categories) when that tool supports it, so you can use the full workspace without opening another route. |
| Scope | A single page can go very deep on one format or workflow. | Broad coverage in one project: many everyday utilities with room to grow—we do not aim to replace every specialized service, but to be a strong default for routine work. |
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 & LLM integration. Toolcore exposes a machine-readable list of tools and URL query conventions for opening a page with prefilled text (most transforms run client-side unless a page says otherwise). See /agent-tools.json for the manifest; /mcp-tools.json lists the same contract without AIGC entries. Use q / qb (Base64 UTF-8) on tools that accept a primary payload, or the per-tool keys described there (e.g. JSON compare uses left / right). The manifest includes an integration block (URL manifest pattern) and an 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.
How it works
The site is built for static delivery and responsive client components so pages stay fast and predictable. Pick a tool from the home catalog or the top navigation (including the "All" menu for hubs such as JSON and Color). Most items above run primarily in your browser unless a specific page says otherwise. An optional account (Google or GitHub sign-in) when this site offers sign-in; when signed in, your profile shows your name and avatar; you can also customize which tools appear on the home catalog and pin some for inline use on the home page, or send signed-in feedback (bugs and feature requests). For site policies, see Privacy; optional support is on Tip & support.