Bulk Path & Filename Slugifier

Convert messy URLs, file paths and filenames into URL-safe slugs while keeping / segments and dropping extensions and query strings.

No uploadsNo sign-upInstant results
URL PathsLive Slugify100% Local • Zero Uploads
Download
Offline engine ready100% private in-browser workspace • Zero cloud uploads
100% Private • Zero Server File Uploads

Why Use Utiliome's Free Bulk Path & Filename Slugifier?

Built from the ground up for strict privacy, instant execution, and zero friction. No subscriptions, paywalls, or account registrations required.

Keeps Folder Structure Intact

Preserves forward slash (/) path delimiters, slugifying each path segment independently.

Extension & Query Cleanup

Optionally strips file extensions (.html, .php), query parameters (?utm=...), and hash fragments.

Batch Multi-Line Route & Sitemap Sanitization

Paste hundreds of legacy URLs, file paths, or S3 object keys at once to generate a clean 1-to-1 redirect or route migration table in browser memory.

Domain, Extension & Query String Stripping

Automatically drops leading https://domain.com origins, .html/.php/.aspx extensions, ?utm=... query strings, and #hash fragments while keeping / folders.

Utiliome vs Traditional Cloud Alternatives

Compare our local-first WebAssembly engine against legacy cloud tools.

Feature Utiliome (Local Browser) Legacy Cloud Converters
Directory Hierarchy (/) Preservation Slugifies each /segment/ independently while preserving folder path structure Destroys forward slashes, turning /docs/v2/guide into docs-v2-guide
Legacy Extension & Query Cleanup Automatically strips .html, .php, .aspx, ?query=1 & #hash anchors Turns .html?id=1 into ugly -html-id-1 suffix tokens on every URL
Percent-Encoded Input Decoding Decodes %20 and UTF-8 %XX sequences first before transliterating to clean slugs Literalizes %20 into -20-, producing my-20-file-20-name slugs
100% Local Sitemap & Route Privacy Sanitizes unreleased site structures and file trees locally in browser RAM Uploads internal URL inventories to external servers
How it works

How to Use Bulk Path & Filename Slugifier in 3 Easy Steps

No software installation required. Everything runs directly inside your web browser.

1

Input URLs or Paths

Paste web links, directory paths, or filenames into the editor.

2

Select URL Sanitization Options

Toggle extension stripping, query parameter removal, path preservation, and separator style.

3

Copy Sanitized Web Paths

Copy the clean URL-safe routes for web routing configuration and static site generators.

Clean URLs and Paths While Keeping Their Segments

Quick Answer: Utiliome sanitizes messy URLs, nested directory paths, and raw filenames into clean, lowercase, hyphenated web routes by decoding percent-escapes (%20), stripping origins and file extensions (.html, .php), and slugifying each forward-slash (/) path segment independently. All computation executes 100% locally in your browser with zero server uploads.

Web routing frameworks (such as Next.js, Astro, and Express) require clean URL segments that do not contain spaces, query delimiters, or file extensions. The URL slugify tool converts unstructured web strings into clean URL paths:

Given this raw web address:

https://example.com/docs/v2.0/User Profile & Settings.html?ref=twitter#overview

With path preservation, query stripping, and extension removal enabled, the tool produces:

/docs/v2-0/user-profile-and-settings

Each path segment is slugified individually, preserving directory structure while stripping .html, ?ref=..., and #overview.

To turn an article title into a slug with stop-word removal, use Slug Generator.

What Gets Removed: Extensions, Queries and Hosts

Quick Answer: When migrating a legacy CMS, SharePoint folder export, or static file tree to Astro, Next.js, or NGINX, preserving directory slashes while cleaning spaces, ampersands, and query parameters produces ready-to-use canonical route paths in one pass. All computation executes 100% locally in your browser with zero server uploads.

When incorporating generated slugs into website architecture, observe these constraints:

  • Segment-by-segment slugification: When Preserve Path Slashes is active, each directory level is slugified on its own, maintaining nested hierarchies like /blog-section/post-name.
  • Query and extension removal: Strips trailing file extensions (.html, .php, .pdf, .jpg, .zip and other common types) and query parameters (?utm_source=...) to form clean canonical permalinks; the extension is removed even when you choose to keep the query string.
  • Domain handling: A leading https://host, //host, www.host or example.com/ is dropped so only the path is slugified; a bare filename such as report.pdf is kept and cleaned.
  • Transliteration support: European, Cyrillic and Greek letters and common symbols are transliterated into URL-safe ASCII; letters from other scripts (for example Chinese or Arabic) are removed. Percent-encoded characters such as %20 are decoded first.

URL Slugify vs Slug Generator: Which Tool Should You Use?

Quick Answer: Use this Bulk Path & Filename Slugifier to clean existing URLs, nested /folder/subpath/ routes, and filenames while keeping / structure and stripping .html or ?query strings; use Title to SEO URL Slug Generator for turning article headlines into short keyword slugs.

The two tools share the same sanitising rules but differ in what they expect as input:

URL Slugify (this page) Slug Generator
Input Existing URLs, file paths, filenames Article titles, headings, product names
Keeps / path segments Yes, cleans each segment separately No, produces a single slug
Strips file extensions and query strings Yes Not needed
Stop-word removal (the, a, and, for) No Yes, optional
Maximum length limit No Yes

If you paste a plain title here you will get a valid slug, but the Slug Generator produces a shorter, keyword-focused result for headlines.

Legacy URL Migration & Path Normalization Examples Table

Quick Answer: Migrating legacy web servers (IIS .aspx, Apache .php/.html, or cloud storage buckets with spaces and percent-encoding) to modern clean-URL routers requires stripping protocol/host prefixes, decoding %20 sequences, removing extensions, and normalizing each path segment. All computation executes 100% locally in your browser with zero server uploads.

See how Utiliome transforms real-world messy URLs and file paths into canonical web routes:

Raw Input URL or File Path Sanitized Output (Preserve /, Strip Ext & Query) Transformations Applied
https://example.com/Docs/V2.0/User Guide.html?ref=nav#top /docs/v2-0/user-guide Drops host, query, hash & .html; slugifies segments
/Products & Services/Café Equipment/Espresso_Machine.php /products-and-services/cafe-equipment/espresso-machine Expands &, transliterates é→e, strips .php
/assets/2026%20Annual%20Report%20(Final).pdf /assets/2026-annual-report-final Decodes %20 first (no -20- bug!), strips .pdf
C:\Marketing\Summer Campaign\Hero Banner.PNG /marketing/summer-campaign/hero-banner Normalizes Windows backslashes & strips .PNG

Explore companion URL utilities: Title to SEO URL Slug Generator, URL Parser, Query String Parser, and URL Encoder & Decoder.

FAQ

Bulk Path & Filename Slugifier FAQ and Technical Guide

Everything you need to know about using Utiliome's free online url slugify.

Can this tool preserve subdirectory slashes while cleaning path segments?

Yes. With the Preserve Path Slashes option enabled, the tool keeps "/" separators intact and sanitizes each directory and file segment individually.

How does the tool handle file extensions and URL query strings?

It automatically detects and strips query strings ("?key=value"), hash anchors ("#section"), and file extensions (".html", ".php") when configured.

What is the difference between slugifying a URL and generating a slug from a title?

Generating a slug turns a free-text title into a single keyword string, usually dropping filler words. Slugifying a URL cleans something that is already a path: each folder segment is sanitised on its own, slashes are kept, and file extensions or query strings are removed. For titles use the Slug Generator; for paths and filenames use this tool.

Why should URLs avoid spaces, uppercase letters and special characters?

Spaces become %20, uppercase letters create duplicate URLs on case-sensitive servers, and characters such as ?, #, & and + have reserved meanings in a URL. A clean slug avoids all of these, so links work everywhere and search engines see one canonical address.

Why do other slug tools turn "My%20File.html" into "my-20-file-html"?

Naive slugifiers run a regex replace on the raw string without URI-decoding first, turning "%20" into "20" and ".html" into "-html". Utiliome decodes percent-encoded sequences (%20 → space) and strips file extensions before slugifying each path segment.

Can I slugify a flat filename without preserve-slashes adding a leading slash?

Yes. Toggle the path slash option or paste bare filenames—when your input is a single filename without directory slashes, the tool outputs a clean flat slug.