Handle Slugifier

Turn your name, brand, or phrase into 12 platform-safe handle variations. Click to copy.

Why slugifying matters

Most platforms reject spaces, accents, and most punctuation in usernames. If your real name or brand contains any of those, you need a clean “slug” version — a lowercase, ASCII-only variant that passes every platform’s format check.

From slug to claimed handle

Once you’ve picked a variation you like, check whether it’s actually available across social platforms and matching domains. NameSniper does this in one shot.

Example transformations

See what the slugifier does to common inputs:

  • Marcus O’Brien → marcusobrien, marcus.obrien, marcus_obrien, themarcusobrien, mo
  • München GmbH → munchengmbh, munchen.gmbh, munchen_gmbh, getmunchengmbh
  • The Cool Studio → thecoolstudio, the.cool.studio, tcs, thestudio
  • José Sánchez → josesanchez, jose.sanchez, jose_sanchez, js

Frequently Asked Questions

What transformations does this apply?

It removes accents and apostrophes, lowercases, strips special characters, then generates 12 variations: compact, dotted, underscored, hyphenated, with common prefixes (the, get, real, try) and suffixes (hq, app, co), initials, and first-plus-last combinations.

Does this check if the handle is available?

No — this tool only generates variations. To check availability across 16 platforms at once, use NameSniper's full checker linked below.

Why does it remove hyphens sometimes?

Hyphens are not allowed on most platforms (Instagram, Twitter/X, TikTok, etc.) so the "compact" and "dotted" variations strip them. The "hyphenated" variation is included in case you want it for domains.

Will my data be sent anywhere?

No. This tool runs 100% in your browser. Nothing is sent to any server.

What happens to accented characters like é or ü?

They're unfolded via Unicode NFKD normalization, then the diacritics are stripped. München becomes munchen, José becomes jose, françois becomes francois. This keeps the pronunciation recognizable while passing every platform's ASCII-only rules.

Does it work for non-Latin scripts like Chinese or Arabic?

Limited. NFKD normalization only separates diacritics — it cannot transliterate characters. Chinese, Arabic, Cyrillic, and other non-Latin scripts are stripped entirely because they do not decompose to ASCII. If your name is non-Latin, you will need a transliterated version as your social handle.

Why only 12 variations and not more?

After 12 reasonable patterns, the returns diminish sharply — you end up with awkward combinations that no one would actually pick. We cap at 12 to keep the list scannable. For more creative variations, the Handle Generator tool explores a different pattern space (prefixes and suffixes).

Can I see the transformation steps?

The pipeline is: (1) Unicode NFKD normalize, (2) strip diacritic marks, (3) lowercase, (4) remove apostrophes, (5) replace remaining non-alphanumeric with spaces, (6) split into words, (7) rejoin in various patterns. Each variation you see is one of the final rejoin strategies.

Is this the same as a "slug" in web development?

Similar concept. A URL slug turns "My Blog Post!" into "my-blog-post" for clean URLs. This tool does the same normalization but generates multiple rejoin strategies (compact, dotted, underscored, hyphenated) because different platforms accept different separators.

Check All Platforms at Once

Don't check one platform at a time. NameSniper checks domains, social media, and trademarks in a single search.

Try NameSniper Free

Continue Reading

Related Tools

Guides

Blog Posts