Slug Generator

A slug is the human-readable tail of a URL, the "my-first-post" in /blog/my-first-post. This tool takes a title, heading, or product name and turns it into that lowercase, hyphenated form so the address stays readable, stable, and safe to type or share. It fits the moments where you are naming a thing that will live at a URL: blog posts and articles, product and category pages, documentation headings, landing-page paths, and help-center entries.

Beyond the web, the same output works well as a safe base for filenames and folder names, since it contains only lowercase letters, digits, and hyphens: no spaces, punctuation, or accented characters to break a shell command, a CSV column, or a download. Developers reach for it when seeding a database column, a CMS field, or a static-site frontmatter key; writers and admins use it to keep a long list of titles consistently formatted before import.

It is not an SEO scoring tool, a redirect manager, or a uniqueness checker. It formats one piece of text into one slug. Deciding whether that slug reads well, avoids keyword stuffing, and does not collide with an existing URL is still your call.

Paste or type your text into the input box and press Run (or Cmd/Ctrl+Enter). The result appears in the output box, ready to Copy to the clipboard or Download as a plain .txt file. Everything happens in your browser; on this site the text is not uploaded, and nothing is retained once you close the tab. A sample loads on open so you can see the shape of the output before typing anything.

The transform is deterministic and applied in a fixed order: letters with no accent to strip are spelled out (ß to ss, æ to ae, ø to o, ł to l), Unicode is normalized and combining accent marks are stripped (so "Café" becomes "cafe"), text is lowercased and trimmed, an ampersand is expanded to the word "and", every run of non-alphanumeric characters collapses into a single hyphen, and any leading or trailing hyphens are removed. The result is always lowercase a–z, 0–9, and hyphens.

What it does not do: it does not truncate to a maximum length, deduplicate against URLs you already have, strip common stop words, offer a custom separator (underscore or other), or transliterate non-Latin scripts into Latin letters. There is one slug style, applied uniformly to whatever you give it.

The most important pitfall concerns non-Latin text. Accented Latin letters decompose cleanly (ü to u, ñ to n) and ß, æ, ø, ł, œ, đ and þ are spelled out, but characters from other writing systems (Cyrillic, Greek, Arabic, Hebrew, Chinese, Japanese, Korean) and emoji are not romanized. They are treated as separators, so a title written entirely in such a script leaves nothing to use, and the tool says so rather than returning an empty slug. If you need a readable slug for those languages, write or transliterate the Latin form yourself before pasting.

Watch the ampersand rule too: "R&D" becomes "r-and-d", which may not be what you intended for an acronym. Numbers, currency symbols, and units lose their symbols ("$50/mo" becomes "50-mo"), and text made only of punctuation or symbols gets the same "nothing usable" message. Because there is no length cap, a long sentence produces a long slug, trim the input first if you want a short path.

Finally, the tool formats; it does not verify. Two different titles can normalize to the same slug, and the tool will not warn you. Pasting a multi-line list produces one slug from the whole block, with line breaks turned into hyphens, rather than one slug per line.

Read the output once before using it. Confirm it is not oddly short (a sign that part of your title was in another script and was dropped), that it has no leading, trailing, or doubled hyphens around removed symbols, and that the words still read clearly out of context. Check that ampersands, numbers, and any acronyms came through the way you meant, and shorten an over-long result by editing the input and running again.

Before publishing, verify the slug is unique against URLs that already exist on your site, and prefer keeping a published slug stable, changing it later breaks existing links and bookmarks unless you set up a redirect. If you are seeding filenames or database keys, also confirm the format matches what your system expects (some require it not to start with a digit, or cap the length).

For anything official, financial, or legally significant (invoice references, regulated document identifiers, account-linked paths), treat the generated slug as a draft and check it by hand against your own naming rules and the authoritative source. This tool is a formatter, not a validator, and it makes no correctness guarantee about identifiers it has no way to know.