Articles · What's new

What's new on Toolcore

A workflow tour of recently added browser tools—text cleanup, deeper JSON helpers, config conversion, network utilities, and PDF work. For how to browse the site itself, start with the site guide.

Toolcore keeps growing, but a long catalog only helps when you can see where each page fits. This is a what's new tour through recent Writing, JSON, Protocol, Encoding, PDF, and media tools, grouped by the kinds of messy jobs they solve.

If you have never opened the catalog before, start with How to use Toolcore first. That guide covers search, the All menu, Client badges, and favorites. Here the question is simpler: when a paste, config file, URL, or document lands on your desk, which newer page should you try first?

When pasted text is messy

Email threads, chat exports, and log snippets rarely arrive clean. They come with odd wrapping, trailing spaces, half-useful quoting, and rows you need to reshape before the real work starts. The newer line tools are meant to be chained in small steps:

A practical order is trim, dedupe lines if needed, split or join, then pad or number. Each step is small enough to check with your eyes before you copy the result into a ticket, spreadsheet, or review comment.

JSON beyond format and compare

Formatting is still the front door, but once a JSON blob is valid, the next question is usually about structure: what changed, what is nested, and what should be removed before sharing. The JSON hub still starts with format and compare, and three newer sub-pages now cover inspection and cleanup:

  • JSON tree viewer — expand nested objects in the browser when a flat textarea is hard to scan.
  • JSON prune — drop nulls or empty values before you ship a smaller payload or fixture.
  • Rename JSON keys — bulk key renames when an API field rename landed in docs but not in your sample file yet.

For config formats outside JSON, YAML ↔ TOML converts directly (handy for Cargo or pyproject-style files) without forcing a JSON stopover. The hub still has JSON ↔ YAML and JSON ↔ TOML when JSON is the pivot you want.

Links and headers are easy to get almost right, which is why they are worth checking with a dedicated page before you paste them into docs, curl, or an app setting:

  • UTM builder — add campaign query parameters without hand-editing ampersands.
  • Safelink decoder — unwrap Outlook or Google-style wrapped links from email HTML.
  • Basic Auth header — build an Authorization: Basic … value for curl or API clients (pair with HTTP headers reference pages).
  • HTTP fetch — a lightweight browser-side request checker when you only need status and headers, not a full API client.
  • Docker run → Compose — turn a long docker run one-liner into a starter Compose service block for local experiments.

Network, identity, and “is this string valid?”

The Protocol and Identity areas are for strings that look familiar but still deserve a quick check before they become configuration:

Compare, measure, and evaluate

Sometimes you are not transforming text, you are trying to measure it. These newer pages sit next to the older diff and calculator hubs:

PDF and media extras

The PDF hub now covers merge, split, rotate, compress, watermark, page delete, text extract, and image conversion—all in the browser tab. On the image side, rotate and flip, crop, and watermark round out quick edits without opening a desktop editor.

How to try a page you have not opened before

The easiest way to try a new page is not to memorize the catalog. Search by the word that is already in your task (for example pad, toml, docker) or open Browse tools and filter by Writing, JSON, or Protocol. Most additions ship with a New badge for a couple of weeks. Use that as a hint, but rely on search and category tabs for the full picture.

For the authoritative list of everything live, use About. For automation manifests and prefilled URLs, see AI agents. New catalog entries are wired there alongside the human-facing page so assistants can hand exact work to the same tools you can inspect yourself.

Common use cases

  • Onboard a teammate who already knows the site layout but not the latest Writing and JSON pages.
  • Bookmark as a map before a sprint that involves pasted logs, config files, or email lists.
  • Share alongside /articles/how-to-use-toolcore when someone needs both navigation and a feature snapshot.

Common mistakes to avoid

  • Using line dedupe for duplicate letters

    Remove duplicate lines works per row; remove duplicate characters works inside each string. Pick the page that matches the grain of your data.

  • Assuming YAML↔TOML replaces the JSON hub

    Direct YAML↔TOML is for when JSON is not in the path. JSON hub routes still exist when you want JSON as the middle format.

  • Skipping the Client badge on mixed workflows

    Most tools in this article are Client-side; if you chain into Server or AI pages, read each badge before pasting secrets.

FAQ

Where is the full list of every tool?

Home → Browse tools, the All menu, or /about. This article highlights recent additions grouped by task, not every catalog row.

How is this different from “How to use Toolcore”?

The site guide explains navigation, badges, favorites, and prefill URLs. This post only maps new pages to common jobs.

Do these tools upload my paste?

The pages called out here are Client tools unless their badge says otherwise. Always check the label on the specific page you open.

Will older tools disappear?

No. New pages extend clusters (JSON hub, Writing, Protocol). Older formatters and reference tables stay in place.