Nirmion
Help Find a tool

Remove combining marks with a controlled scope

Accent Remover

Remove decomposed combining marks from Latin-script letters only or from every script, while preserving non-decomposing characters and reporting how many marks changed. This is mark removal, not transliteration: letters such as ł, ø, đ, æ, œ, and ß may remain, and all-script mode can damage meaning in languages that require marks.

  1. 01Private by designYour text stays in this browser tab.
  2. 02Bounded and responsiveUp to 500,000 characters in each main text field.
  3. 03Ready to reuseCopy the result or download a branded TXT file.
No text upload to Nirmion

Counting and transformations run locally. Nirmion does not send the text in this workspace to an API.

01 / Input

Paste text and choose the mark-removal scope

Use Latin-only mode for a narrower cleanup, or choose all combining marks only when the downstream contract explicitly requires destructive mark removal across scripts. Input is bounded to 500,000 characters; text is canonically decomposed for inspection and recomposed after selected marks are removed.

Complete the required fields to enable this action.

Runs in this tab without an API request.

Product guide

Distinguish accent stripping from transliteration

Combining-mark deletion can help a legacy matching key, but it is lossy and does not create a correct ASCII representation of every language or name. Review the complete result in its destination because automated text rules cannot infer every language, house style, data model, or publishing intention.
Step A

Prepare the input

Paste representative text and keep a source copy. Include non-Latin examples when testing all-script mode so damage is visible before adoption.

Step B

Choose the rule

Latin-only mode removes marks only when the preceding decomposed base belongs to Latin script. All-combining mode removes every Unicode mark after decomposition.

Step C

Review the output

Use the output as a secondary search or import key where approved, not as a replacement for authoritative names, language content, legal text, or display copy.

How it works

Canonical decomposition followed by scoped mark deletion

The source is normalized to NFD and inspected by Unicode code point. In Latin scope, a combining mark is removed only when its current base character has Script=Latin; all-combining scope removes every mark. The remaining sequence is normalized back to NFC, and non-decomposing letters are left untouched. The source cap is 500,000 characters and output cap is one million; no transliteration table, language model, or external identity service is used. The operation runs in this browser tab, applies explicit bounds before expensive work, and does not send workspace text to a Nirmion API.

Useful when

Create a reviewed secondary comparison key

Use accent removal only when a documented compatibility requirement outweighs the loss and original text remains available.

  1. Test accent-insensitive search keys while retaining the original correctly spelled value for display.
  2. Preflight a legacy export or identifier policy that explicitly permits Latin combining-mark removal.
  3. Demonstrate why all-script mark deletion is unsafe by comparing multilingual input and output before implementation.

Questions answered

Accent Remover questions

Practical boundaries matter with text tools. These answers explain what is measured, what is retained, and when a manual review is still needed.

Why did Ł or ø remain?

Those letters do not decompose into a basic Latin letter plus combining mark under canonical NFD, so mark removal alone does not transliterate them.

Is Latin-only mode safe for names?

It is narrower, not lossless. Removing an accent can still change a person or place name and should not replace authoritative display data.

What does all combining marks do?

It removes marks from every script after decomposition and can severely alter non-Latin text. Use it only for an explicit technical contract.

Privacy and retention

Your draft stays on your device.

Nirmion performs these operations with browser JavaScript. The workspace does not call the catalogue API with your source text, and completed-job content is kept only in this component memory for re-download.

A downloaded file remains in your browser downloads, device storage, backups, and any location where you share it. Clear or close the page when working on a shared device, and avoid pasting secrets into extensions or third-party clipboard managers.

Tool details

Scoped accent removal with no transliteration claim

Nirmion Accent Remover decomposes Unicode text, then removes combining marks from Latin-script bases or from every script according to an explicit scope. It reports removed marks and character counts so users can inspect a lossy compatibility transformation rather than accepting a hidden rewrite. The source is normalized to NFD and inspected by Unicode code point. In Latin scope, a combining mark is removed only when its current base character has Script=Latin; all-combining scope removes every mark. The remaining sequence is normalized back to NFC, and non-decomposing letters are left untouched. This makes the behavior inspectable and repeatable instead of presenting an unexplained result.

Output downloads as text_nirmion_tools_accents_removed.txt for source up to 500,000 characters. The page explains non-decomposing letters, multilingual damage, name integrity, authoritative source retention, and the difference between stripping and transliteration. The operation runs in this browser tab, applies explicit bounds before expensive work, and does not send workspace text to a Nirmion API. Downloading clears the active workspace while the latest three completed results remain available in this tab for re-download.