Replace Accents: easy way to remove and restore diacritics

Common pain points with diacritics and ASCII only systems

Most teams see the same problems repeat across content, code, and data exports. These issues hit copywriters, content editors, and developers in slightly different ways but share the same root causes.

• ASCII only backends and exports: older databases, flat file integrations, and legacy APIs accept only ASCII, so č, ű, å, ñ vanish or turn into broken characters.
• Unsafe URLs and slugs: CMS or custom routing layers accept non ASCII characters but downstream tools, CDNs, or logs do not, which forces you to create ASCII only slugs for safety.
• Manual accent removal: you copy text into browser converters, online slug generators, or one off scripts, then paste results back into VS Code, which wastes time and invites mistakes.
• Text typed without diacritics: someone write cafe, donde esta, szep zold haz for speed, and you must turn this into correct spelling before publishing or translating.
• Mixed Unicode data: emojis, combining marks, and mixed scripts confuse naive replacements, which strip more than diacritics and corrupt content.

Reduce context switching and standardize workflows

Using a VS Code extension for diacritics and ASCII folding gives you a repeatable workflow that everyone on the team can share. You stay in the editor, apply the same rules each time, and avoid hidden one off scripts sitting on someone’s laptop.

• Run accent removal or restoration from the Command Palette or a keyboard shortcut.
• Apply rules to selections, whole files, or multiple files inside the VS Code workspace.
• Store configuration in project level settings, so new team members get the same behavior.
• Keep sensitive content inside the editor instead of pasting text into random web tools.

What Replace Accents does under the hood

The extension translates Unicode know how into simple commands that work across many languages. It hides complex logic behind a small and clear surface.

• Normalizes text with Unicode NFKD, which decomposes letters and diacritics.
• Strips combining diacritical marks while leaving base characters and emojis intact.
• Applies language specific ASCII mappings such as ä to ae and ß to ss.
• Restores diacritics using frequency ordered word lists for each supported language.
• Supports optional suffix matching for stems plus inflected endings.
• Lets you define custom mappings and ignore lists for project or brand rules.
• Works on text selections, full documents, and file or folder names in VS Code Explorer.

Unicode based diacritic removal that is safe for emoji

Many simple remove accents utilities treat characters as single bytes and guess replacements. Replace Accents uses Unicode NFKD normalization, which decomposes characters into base letters plus combining marks, then removes only the marks.

For example, á becomes a plus a combining acute accent that the extension strips, leaving a. The same logic applies to ő, ć, or ñ, but emojis and other symbols stay untouched. café ☕ turns into cafe ☕ and naïve résumé becomes naive resume without affecting emoji or multibyte characters.

This matters whenever you:

• Prepare data for ASCII only systems and APIs.
• Build accent insensitive search indexes where cafe should match café.
• Export content to older databases that cannot handle full Unicode.
• Generate identifiers or keys from human readable titles inside VS Code.

Language specific ASCII mappings for German, Nordic, and Central European text

After normalization, Replace Accents can apply language specific ASCII foldings where conventions exist. This keeps text readable even when you must restrict yourself to pure ASCII.

For many Central European characters there is no standard digraph, so the extension maps them to base letters.

These mappings are ideal when you generate SEO slugs, filenames, or identifiers that must be ASCII but still understandable to native speakers. A German phrase like größerer Überblick becomes groesserer ueberblick instead of a broken groserer uberblick.

Smart diacritic restoration with dictionaries and suffix matching

Restoring accents is harder than removing them. Replace Accents tackles this by using per language word lists that cover words with at least one non ASCII character. Each list is ordered by frequency, so common words are preferred when several candidates exist.

When you run accent restoration, the extension scans each word in your text, checks the chosen dictionary, and replaces plain Latin forms with likely accented variants. If suffix matching is enabled, it can combine stems and endings, which helps in highly inflected languages.

Realistic examples:

• Hungarian edenyemet becomes edényemet when using the Hungarian dictionary even though the dictionary only containt the word edény.
• szep zold haz becomes szép zöld ház across a paragraph typed without accents.
• Czech stredni skola becomes střední škola once you select the Czech dictionary.
• Spanish cafe con leche turns into café con leche in one step.

You still review changes, but the extension performs the heavy lifting and lets you correct edge cases manually instead of fixing every word by hand.

Custom character mappings for brands and project rules

Every project has its own quirks. Brand names, product lines, and internal identifiers often follow rules that generic mappings cannot predict. Replace Accents lets you define custom character mappings that run after normalization and built in logic.

Typical uses:

• Map œ to oe for a specific brand guideline.
• Force ł to l or lt based on how your company writes Polish names in ASCII.
• Handle rare characters from legacy systems that you always want to collapse to a known form.

You can store these mappings in user or workspace settings. Workspace settings travel with your repository, so everyone on the team gets the same behavior for the same project.

Batch processing and keyboard shortcuts in daily work

Replace Accents is designed for daily use, not just one time migrations. It provides commands for selections, active documents, and multiple files or folders selected in VS Code Explorer.

You can bind comfortable keyboard shortcuts such as:

• One shortcut to remove diacritics from the current selection.
• Another shortcut to restore accents in the selected language.
• Commands bound to Explorer context menus for renaming files and folders.

Over time this becomes muscle memory. You highlight a title, press the shortcut, and instantly have a clean slug or a restored accented version ready for publication.

Generate SEO slugs from accented titles with Dev Toolbox

For URL slugs you have a dedicated helper: the Dev Toolbox extension includes a built in slug generator that handles diacritics and separators for you. You write your title with full accents, then let Dev Toolbox turn it into a URL ready slug in one step.

• Write the title with correct diacritics in markdown or HTML.
• Select the title text and run the Dev Toolbox command that generates a URL slug (slugify).
• Dev Toolbox removes diacritics, normalizes whitespace, and replaces separators with hyphens while keeping file extensions intact when needed.
• Paste the finished slug into the slug or URL field in your front matter or router config.

You keep the accented title for readers and get a stable, ASCII safe slug that follows the same rules every time. Replace Accents remains your tool for more controlled accent removal and restoration elsewhere, while Dev Toolbox focuses on the full slug generation workflow.

You can install Dev Toolbox from the Visual Studio Code Marketplace (opens in new window).

Normalize filenames and assets for static sites and pipelines

Non ASCII filenames can break static site generators, build tools, or deployment environments. Replace Accents can rename files and folders directly from the VS Code Explorer using the same accent removal logic as for text.

Typical flow:

• Select image or content folders that contain accented filenames.
• Trigger the Rename command from Replace Accents in the Explorer context menu.
• Review the preview of name changes and confirm.
• Commit the changes as part of a migration or cleanup branch.

A file like őszi-képek/legyelő-szarvas.jpg becomes oszi-kepek/legyelo-szarvas.jpg, which is simpler for tools that assume ASCII only paths. If you need stricter naming rules or further transformations on the resulting names inside your code or configuration files, Dev Toolbox can apply those as additional text utilities.

Fix imported data and legacy exports with stripped diacritics

Many systems store or export content without accents, especially older ERPs and CSV based integrations. Replace Accents lets you restore diacritics before that data hits the public website or documentation.

• Open the CSV, JSON, or text export in VS Code.
• Select the columns or blocks of text that should contain accents.
• Choose the correct language dictionary and run the restore command.
• Spot check results and adjust or re run on smaller selections if needed.

Content editors get a fast way to upgrade szep zold haz into szép zöld ház across whole files, and developers can keep the transformation tracked in version control. When you later need ASCII safe keys or identifiers from the same cleaned data, Dev Toolbox can generate those formats without leaving VS Code.

Focused language dictionaries where accents matter

The extension includes word lists for many European languages. Each list contains only words that include at least one non ASCII character, which keeps lookups fast and focused exactly on diacritics.

Because only non ASCII words are stored, dictionaries stay compact but highly relevant. This keeps diacritic restoration targeted and efficient for each language.

Localized UI for multilingual teams

The Replace Accents user interface is localized into several languages, including English, Hungarian, Slovak, Czech, German, French, Polish, Bulgarian, Spanish, Italian, Japanese, Korean, Brazilian Portuguese, Russian, Turkish, Simplified Chinese, and Traditional Chinese.

For distributed teams this means developers and content editors can read prompts, messages, and configuration labels in their own language. That removes friction when onboarding new teammates and lowers the risk of misconfiguring important options.

Key settings you should tune first

A few settings have a big impact on results. Tuning them early gives you consistent behavior across projects.

• Custom character mappings: add overrides for special characters, brand names, or project conventions that must be handled in a specific way after generic ASCII folding.
• Dictionary selection: choose the default language for diacritic restoration per workspace, for example Magyar, Slovenčina, Čeština, Deutsch, Polski, Dansk, Français, Español, or Svenska.
• Suffix matching behavior: enable it when working with narrative text in inflected languages to improve coverage, and consider disabling it for short product names or codes where precision matters more than coverage.
• Ignore list for brands and acronyms: add words that should never change, such as brand names, product codes, or technical acronyms that must stay unaccented.

Store these settings in workspace configuration so everyone on the project gets the same diacritic behavior and slug generation rules.