DEVELOPER TOOLBOX

Sixteen small tools for the jobs that interrupt real work: generate an ID, hash a download, build a security header, check a config, or look up a status code. Every one runs on this page, with no account and no upload.

Zero retention: your data never leaves this browser. Verify it yourself in DevTools

Loading the toolbox.

About 2toolbox

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word that your data stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your data.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Use the tool with your own input.
  5. Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and the tool keeps working.

Only two things can add a line to that log, and neither carries your data. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.

The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your data elsewhere.

What Is 2toolbox?

2toolbox is a free collection of developer utilities that run entirely in your web browser. It gathers the small, frequent jobs that otherwise send you to a different website each time: generating a UUID, hashing a file, converting hex to binary, building a Content-Security-Policy, writing an .htaccess or robots.txt, checking an XML document or an SSH config, and looking up an HTTP status code or a MIME type.

Each tool has its own page and address, so you can bookmark the ones you use. All of them share one design, one privacy model, and one small script, so moving between tools is fast and nothing about the experience changes.

Why Does a Client-Side Toolbox Matter?

Developer utilities see sensitive input. A .env file holds database passwords. A TOTP secret is the second factor of an account. An sshd_config describes how a server lets people in. Many online tools send what you paste to a server, where it can be logged, cached, or kept. A tool that never receives your data has nothing to leak.

Every 2toolbox tool does its work with code that is already in your browser tab. Hashes and TOTP codes use the browser's own Web Crypto API. Parsing, validation, and generation are plain JavaScript on the page. The page makes no request while you work, and you can confirm that yourself in about a minute with the steps above.

What Tools Are in the Generators Lane?

Generators produce a file or value you can paste straight into a project.

  • 2uuid makes UUID v4 and v7, ULID, and NanoID identifiers in bulk, and decodes the timestamp inside v1, v6, v7, and ULID values.
  • 2gitignore merges ignore rules for your languages, frameworks, operating system, and editor into one de-duplicated .gitignore.
  • 2csp builds a Content-Security-Policy header or meta tag, including nonces, hashes, strict-dynamic, frame-ancestors, and Report-Only mode.
  • 2htaccess writes Apache rules for HTTPS, a canonical host in a single redirect, compression, caching, security headers, and blocking sensitive files.
  • 2robots writes a robots.txt with your sitemap, private paths, an optional crawl delay, and an optional block for AI crawlers.

What Tools Are in the Encode and Crypto Lane?

These tools compute values with real cryptography or exact arithmetic.

  • 2hash computes MD5, SHA-1, SHA-256, SHA-384, and SHA-512 for text or a file up to 1 GB, computes HMACs, and checks a download against a published checksum.
  • 2base converts between binary, octal, decimal, hexadecimal, and any base up to 36, with a clickable bit grid and signed two's complement views up to 64 bits.
  • 2otp shows live TOTP codes from a base32 secret or an otpauth URI, honors SHA-1, SHA-256, and SHA-512, and proves itself against the published RFC 6238 test vectors.

What Tools Are in the Checkers Lane?

Checkers read something you paste and report problems with line numbers.

  • 2xml formats, minifies, and validates XML, lints namespaces and duplicate siblings, and converts XML to JSON and back.
  • 2jq runs a labeled subset of jq, covering paths, pipes, select, length, and keys, against JSON you paste.
  • 2ssh validates sshd_config and ssh_config files, flags weak algorithms and risky settings, and composes the right ssh-keygen command.
  • 2dotenv finds duplicate keys, empty values, and quoting mistakes in a .env file, compares it with .env.example, and generates one.
  • 2kbd shows the key, code, keyCode, location, and modifiers of any key you press, with a ready-made event handler.

What Is in the References Lane?

  • HTTP status codes: every code in the IANA registry with its defining RFC and a plain-English meaning.
  • MIME types: about 150 file extensions and the Content-Type to serve them with, searchable both ways.
  • Quick index: describe the job, find the tool.

The two reference tables live here for now and may move to a dedicated HTTP tool later.

How Do You Use 2toolbox?

  1. Pick a lane at the top of the workbench: Generators, Encode / Crypto, Checkers, or References.
  2. Choose a tool from the row beneath it. Each opens on its own page with a working example already filled in.
  3. Replace the example with your own input. Results update as you type.
  4. Copy or download the result. Generated server files are good defaults; test them on staging before production.

How Does 2toolbox Handle Secrets?

Two tools are built for input that is genuinely secret: 2otp, which takes a TOTP seed, and 2dotenv, which takes a .env file. Both send no analytics events of any kind, keep what you paste only in the memory of this tab, and never write it to storage or to the address bar. The 2otp field is masked by default with a reveal toggle, and autocomplete, spellcheck, and password managers are switched off for it.

Both tools wipe their input when you leave the tab, switch to another tool, or stop interacting for a few minutes. Each shows a red notice inviting you to verify all of this in the Network tab. Even so, the best habit is to test with a throwaway secret, and both tools say so on the page.

Who Is 2toolbox For?

  • Web developers shipping security headers, redirects, and robots rules.
  • Backend and platform engineers checking SSH, environment, and XML configuration.
  • Anyone wiring up 2FA, webhooks, or checksums who needs a known-good value to compare against.
  • Students learning how hashing, number bases, TOTP, and HTTP work, with real output to experiment on.
  • Anyone who works under a policy that forbids pasting data into third-party services.

Part of the 2suite.io privacy-first ecosystem. Working with JSON in depth? 2json is the full JSON workbench. Testing a regular expression? Try 2regex.

Frequently Asked Questions

Is 2toolbox free?

Yes. Every tool is free, with no account, no usage limits, and no paid tier.

Is anything I paste uploaded to a server?

No. Every tool runs in your browser, so your data never leaves this browser. Nothing you type or paste is uploaded or stored, and only your theme is remembered between visits.

Does 2toolbox collect any analytics?

Yes, one anonymous page-view count when a page loads, before you can type anything. It records the app name, the event name, and a random ID for that browser tab. If you submit the feedback form, your vote, your comment, and your browser type are sent too. Nothing you enter into a tool is ever included.

Why does each tool have its own page?

So you can bookmark and share the tool you need, and so each one can explain itself properly. All pages share the same small script, so switching tools is quick.

Is it safe to paste a real 2FA secret or .env file?

The tools are built so that it is: no network calls, memory only, masked input, and automatic wiping. The safest habit is still to test with a throwaway secret or a copy with placeholder values, and both tools remind you of that.

Does 2jq support the full jq language?

No. It is a clearly labeled subset covering paths, pipes, select, length, and keys. For anything deeper, use real jq or the 2json workbench.

Can I use the generated files in production?

Yes, after review. The CSP, .htaccess, robots.txt, and .gitignore output are sensible defaults, but every server and site differs, so test on staging first.

Does 2toolbox work offline?

Once a page has loaded, every tool keeps working with the network turned off, because all the work happens in the page itself.

Was this helpful?