About BeautifyText

BeautifyText is a small collection of text utilities built on a simple premise: the fastest, safest tool for cleaning up text is one that runs on your own machine and asks nothing of you.

Why this site exists

Most online text tools are wrapped in advertising, cookie banners, account prompts and upload forms. Many of them send the text you paste to a server, which is a strange thing to do with a contract, a draft article or a list of customer addresses. Others are so heavily scripted that they take seconds to become usable on a phone.

This site takes the opposite approach. Each page loads a small stylesheet and one JavaScript file, then does all the work locally. There is no upload, no account, no tracking and no cookie notice, because there is nothing to disclose.

What is on the site today

Four tools is deliberate. Each one is finished, documented and tested rather than one of forty half-working pages, and each page explains the exact rules it applies so you can predict the result before you paste anything.

How it is built

The whole technology stack, in full
Markup Hand-written HTML5, rendered by shared PHP templates.
Styling One plain CSS3 file using custom properties. No framework, no preprocessor, no utility classes.
Text processing Vanilla JavaScript in a single file, with no runtime dependencies.
Server side PHP 8 rendering templates only. It never receives, parses or stores the text you paste.
Data store None. There is no database and no server-side storage of any kind.
Third-party code None. No analytics, no fonts loaded from a CDN, no advertising, no chat widget.

The practical result is a site that fits comfortably on ordinary shared hosting, needs no build step to deploy, and has no supply chain to keep patched beyond PHP itself.

How the tools are tested

The text transforms are pure functions with no DOM dependency, which makes them testable directly. They are checked against edge cases including empty input, input that is only whitespace, Windows, Unix and legacy Mac line endings, mixed scripts, emoji and combining marks, duplicate lines that differ only in case or in invisible trailing spaces, and very long inputs. Where a rule could reasonably go two ways — whether Apple equals apple, for example — the choice is documented on the tool page rather than left to guesswork.

Limits and honest caveats

  • Everything needs JavaScript. The tools run in the browser, so if scripts are disabled you will get the pages and their documentation but no working tools. The pages themselves are plain HTML and remain readable.
  • Sentence case cannot restore proper nouns. It capitalises the start of each sentence; names that were lowercase stay lowercase. Always give that output a read.
  • Very large inputs are limited by your device. Since nothing is sent anywhere, the ceiling is your browser's available memory rather than a server quota.
  • No accounts or sync. Text is not saved between visits, on purpose. Copy anything you want to keep before closing the tab.

Suggestions are welcome

Bug reports, corrections and tool requests genuinely shape what gets built next. There is no contact form and no tracking pixel, so send a normal email — the address is on the contact page.