About TextToBinary.net

What this site is

TextToBinary.net is a collection of 47 free tools for developers, SEO specialists, students and anyone who occasionally needs to convert, generate or inspect something and does not want to install software for it.

Alongside the tools there are 8 reference tables and 10 long-form guides. The guides exist because most tool sites answer “how” and stop there. Knowing that UTF-8 uses one to four bytes per character is more useful than being able to click a button that converts one.

Everything is free, there is no account, and there is no paid tier.

Everything runs in your browser

This is the design constraint the whole site is built around: no input you type is ever transmitted anywhere.

Every tool is plain JavaScript executing in your own browser tab. There is no backend that processes your data, because there is no backend at all — the site is static files. When you paste a JWT into the decoder, hash a password, or convert a customer list, those bytes never leave your machine.

You can verify this rather than take our word for it:

1. Open your browser’s developer tools and watch the Network tab while using any tool. There are no requests.
2. Load a page, disconnect from the internet, and keep using it. Everything still works.
3. View the page source. All the logic is there, unminified and readable.

The practical consequence is that this site is safe for data you would not paste into an unknown web service. That was the point.

How the tools are built

• No frameworks and no dependencies. Plain JavaScript, plain CSS. Pages are typically 25–40 KB in total and load on any connection.
• Standard browser APIs. Web Crypto for hashing and randomness, TextEncoder and TextDecoder for character encoding, the URL API for parsing, Canvas for rendering. Standards rather than reimplementations.
• Specification-driven. Where a tool implements a standard, it follows that standard and cites it. Sources are listed at the bottom of every page.
• Accessible. Semantic HTML, labelled form controls, ARIA live regions on outputs, full keyboard operation, and WCAG AA contrast throughout.
• Honest about limits. Where a tool is approximate — the conservative minifier, the pragmatic email pattern — the page says so rather than implying more precision than exists.

Editorial standards

The written content follows a few rules:

• Primary sources. RFCs, W3C and WHATWG specifications, the Unicode Standard, NIST publications, MDN and official search engine documentation. Every article links to what it drew on.
• No invented statistics. Figures are either cited or clearly labelled as approximations. There are no fabricated user counts, ratings or testimonials anywhere on this site, and no review markup claiming any.
• Corrections over silence. If something here is wrong, the page gets fixed and the modification date updated. Reports are welcome via the contact page.
• Uncertainty stated. Where search engine behaviour is inferred rather than documented, the text says so.

Who builds it

The site is built and maintained by Thibault Besson-Magdelain, a software engineer working on data encoding, web standards and search technology. It started as a set of scripts kept in a scratch file and turned into a website when it became obvious the same conversions kept coming up.

There is no company behind it and no team. If a tool behaves oddly or a guide is wrong, one person reads the report.

LinkedIn · Contact

How the site is funded

Running a static site costs very little, which is why the tools can be free with no account and no data collection.

Some outbound links to third-party products may be affiliate links, meaning a commission could be earned if you buy something after following one. This never affects what is recommended, and it never affects the tools, which are free regardless. Where such links exist they are marked, and the full position is set out on the disclaimer page.

What is not done: selling data (there is none to sell), gating features behind a signup, or inserting tracking into the tools.

Maintenance

Pages carry a “last updated” date, which reflects genuine review rather than an automated timestamp bump. The maintenance cycle is:

• On report: bugs are the priority and get fixed first.
• Quarterly: tools are re-tested across Chrome, Firefox, Safari and Edge on desktop and mobile.
• Annually: content is reviewed against current specifications and search engine documentation, since both change.

If a page cites something that has since been superseded, that is a bug too. Please report it.

Frequently Asked Questions