ToolzyLab
Rename JPG, PNG, WEBP, SVG, HEIC, AVIF, BMP, GIF, TIFF and PDF files in bulk with smart numbering, find & replace, prefix, suffix, and custom patterns. Everything stays local and private in your browser.
Rename hundreds of files cleanly with numbering, custom naming rules, and safe duplicate handling. No uploads, no waiting, no privacy worries.
Or choose files from your device.
📁 Bulk rename up to 500 files · 💾 Fully local · 🔒 PrivateBatch renaming is safest when the preview communicates the exact final sequence before any ZIP download. Combine a descriptive base pattern with prefixes, suffixes, counters, dates, case rules, and sanitization only when each part serves organization or publishing. Filenames support asset management, but they do not replace accurate alt text or page context.
A pattern such as product-name-front-001 is easier to scan than IMG_4827 or a long string of repeated keywords. Use lowercase and hyphens for web assets when that fits the publishing system, and retain meaningful distinctions such as angle, color, location, or language. Avoid stuffing every possible query into the filename.
Counters preserve the order shown in the preview, so confirm that portraits, event photos, slides, or product angles are arranged correctly first. Choose enough number padding for the batch size: 001 through 120 sorts more predictably than 1 through 120 in many file browsers. Use a stable date format such as year-month-day when chronological sorting matters.
Operating systems, ZIP tools, CMS platforms, and URLs handle punctuation differently. Sanitization and collapsed spaces reduce compatibility problems. Duplicate prevention matters when two source names resolve to the same new pattern. Review extensions separately from base names so an uppercase or lowercase rule does not accidentally misrepresent the actual file format.
Read the proposed names as a list before applying rules; a preview is cheaper to fix than a published folder.
Technical references: Google image SEO filename guidance
Use a short, descriptive filename that identifies the image, such as blue-running-shoe-side.jpg. Lowercase words separated by hyphens are easy to read and reuse. Do not repeat keywords or rely on the filename instead of meaningful alt text.
A descriptive filename can provide modest context and improve asset management, but page content, image quality, surrounding text, alt text, and user experience matter more. Write names for clarity rather than ranking manipulation.
Use a counter with leading zeros, such as 001, 002, and 003. Choose padding based on the batch size and verify the source order before applying the rule.
Yes. Keep Original or pattern tokens can preserve the source base while adding a prefix, suffix, date, or sequence. Use Find and Replace to remove a repeated camera or export fragment when needed.
Enable duplicate prevention and inspect the live preview. The tool should distinguish conflicts, but you should still verify the final list because duplicate handling may add suffixes that affect the intended sequence.
Changing letter case is safe, but renaming .png to .jpg does not convert the file. Preserve the true extension unless a separate format converter rewrites the image bytes.
Year-month-day, such as 2026-08-09, sorts chronologically and remains unambiguous. Use another format only when a team or archive has an established convention.
No. The operation changes downloadable filenames, not visible pixels or embedded metadata. Use the metadata tool separately when EXIF or GPS fields also need review.