Free Text Tools

What these tools are for

Text work is full of small chores that do not deserve an application. You need to know whether a description fits under 160 characters. You need to strip the line breaks out of something copied from a PDF. You need a rough reading time for a draft. Each of these takes seconds if the right tool is in front of you and ten minutes if it is not.

Eliroo's text tools are built for exactly those moments. Each one opens with the input box already focused, works as you type, and gives you the answer without a submit button or a results page. There is nothing to install and nothing to sign up for.

Why they run in your browser

Most online text utilities post your content to a server, process it there, and send the result back. That is simpler to build, but it means your text — which may be a draft of something confidential, a client's copy, or a chunk of internal documentation — has left your machine and now exists on someone else's disk, at least briefly, and in a log file possibly for much longer.

Every tool here works differently. The processing code is delivered to your browser as part of the page and then runs locally, the same way a spreadsheet formula runs locally. Open your browser's network panel while you use one and you will see no request going out. That is not a policy promise you have to trust; it is something you can verify in about fifteen seconds.

Choosing the right tool

If you want to know how long something is, start with the word counter — it reports words, characters with and without spaces, sentences, paragraphs and an estimated reading time all at once, so you rarely need a second tool. If you are cleaning text up rather than measuring it, look for the tools that remove line breaks, collapse repeated spaces or strip duplicate lines. If you are changing its shape — case, sort order, encoding — the case converter and the developer encoders are the place to go.

We are adding to this category steadily rather than all at once, and the tools that go in first are the ones people actually search for. If something obvious is missing, it is probably next in the queue.

Accuracy and edge cases

Text is deceptively hard. An emoji can be one character or five depending on how you count. A Sinhala or Devanagari cluster looks like one letter but is stored as several code points. Naive tools get these wrong and quietly report the wrong number. Where the browser offers a correct implementation — Unicode segmentation, locale-aware collation, proper UTF-8 encoding — we use it rather than rolling our own approximation, and the tool page tells you which definition it applied.

Working with text on a phone

A surprising share of this kind of work happens on a phone — you are away from your desk, someone sends you a paragraph, and you need to check its length before it goes out. Text tools are usually terrible on mobile: tiny inputs, results below the fold, a submit button that reloads the page and loses what you pasted.

Ours are laid out mobile-first. The input box is large enough to actually see what you pasted, the results sit directly beneath it without scrolling, and because everything updates live there is no submit step to lose your work. Buttons are sized for thumbs rather than mouse pointers, and nothing on the page scrolls sideways.

What we do not do

These tools do not rewrite, summarise or generate text, and they do not check grammar. That is deliberate. A tool that transforms your words needs judgement, and judgement means either a large model on a server — which would mean uploading your text after all — or a set of rules that will be wrong often enough to cost you more time than it saves. We would rather do a small number of mechanical jobs exactly right.

Nothing here stores your input between visits either. Close the tab and the text is gone; reopen the tool and you start from an empty box. If you want a draft kept, keep it somewhere designed for that.