About TrenTyx – Free Browser-Based Developer Tools

trentyx@local:~/about $ cat about.md_

TrenTyx is a collection of 24 developer utilities that run entirely in your browser. No accounts, no uploads, no waiting on a server. It exists because the tools it replaces were slower, noisier, and far too eager to see data that was none of their business.

Why This Site Exists

Every developer keeps a mental list of small chores: decode a JWT to check a claim, convert a timestamp, format a query someone pasted into a ticket, diff two JSON payloads, base64 a small image. None of these take long. The problem is what surrounds them. The typical result of searching for one of these tasks is a page carrying several ad slots, a cookie wall, a newsletter prompt, and a form that quietly posts your input to a server you know nothing about.

That last part is the real issue. A JWT often contains a user identifier. A SQL query contains table names and sometimes literal values from production. A hash input might be a password. Pasting any of that into a remote form is a habit worth breaking, and the easiest way to break it is to make the local alternative faster than the remote one.

How It Works

Every tool here is a single HTML page with its logic in plain JavaScript. When you paste something in, the work happens in your browser tab. There is no API call behind the scenes, no queue, and no server-side processing step. You can verify this: open your browser's network panel, use any tool, and watch that nothing leaves the page. You can also save a page and keep using it offline.

The practical consequences are worth stating plainly:

  • Your input stays local. Queries, tokens, images and text are never transmitted, so they cannot be logged, retained or leaked by this site.
  • No sign-up exists. There are no accounts, so there is no account data to protect.
  • Results are instant. No network round trip means output appears as you type.
  • Size limits are your machine's, not a server's. Large inputs are capped only to keep the page responsive, and the caps are stated in each tool.

What Is Here

The 24 tools are grouped into four categories:

  • Data Converters — JSON to and from CSV, YAML and XML, JSON to TypeScript, structural JSON diffing, CSV to SQL inserts, and image to Base64.
  • Text & Encoding — JSON formatting and validation, Base64, URL encoding, Markdown to HTML, case conversion, text diffing, and SQL formatting.
  • Dev Utilities — timestamps, UUIDs, hashes, passwords, JWT decoding, regex testing, cron expressions, number bases, and LLM token counting.
  • Design — colour format conversion.

Each tool page includes a written explanation of the underlying concept, not just a text box. The goal is that reading the page teaches you something about the format, so you need the tool less often over time.

Agent-Friendly by Design

Every tool registers itself through WebMCP, the emerging browser standard that lets an AI agent operating your browser call a page's functionality directly instead of guessing at the interface. If you use an agentic browser, it can format SQL, decode a token or count tokens through these pages without you clicking anything. The pages are also fully keyboard navigable and use proper ARIA landmarks, which benefits screen reader users and agents alike.

Who Maintains It

TrenTyx is built and maintained by Ahmad Fawaid, an independent developer based in Indonesia. It is a personal project rather than a company product, which is why there is no sales team, no pricing page and no roadmap promising features that never arrive.

The site is funded by nothing at the moment. It costs a domain registration and static hosting, which is cheap enough that the tools can stay free without advertising. If that ever changes, this page will say so before anything appears on the tool pages.

Corrections and Requests

If a tool produces a wrong result, that is a bug worth reporting, and the report is genuinely useful because these pages have no error reporting telemetry — nothing tells the maintainer that something broke unless a person does. The contact page explains what to include so a problem can be reproduced on the first try.

Requests for new tools are welcome too. The bar is simple: it has to be something that can run correctly and entirely in the browser, and something a developer needs often enough to justify a bookmark.

Related Pages