Changelog / Product updates
A public record of what changed in WebRenamer: safer batch exports, browser-first file workflows, and the next improvements planned for local file renaming.
Last updated:
01 — Shipped
2026-08 · EXPORT
The export action now derives its count from the exact valid files it will write. Valid unchanged files stay in the replacement ZIP, while files rejected for a conflict or incompatible name are left out and no longer inflate the button label.
2026-08 · ZIP
The browser-generated archive is now checked from response to extraction with an independent ZIP reader. Fixtures cover Chinese, accented Latin, Arabic, and emoji filenames, their original bytes, and the UTF-8 filename flag expected by common desktop archive tools.
2026-08 · QA
The export test set includes names chosen to exercise the parts most likely to differ between Windows and macOS workflows: Unicode normalization, multilingual text, emoji graphemes, unchanged files, and invalid destination names.
02 — Fixed
FIX_01 · COUNT
The download button now says exactly how many files are included in the ZIP instead of repeating the size of the input list. This makes collision and invalid-name warnings visible in the final export step.
FIX_02 · ENCODING
ZIP creation enables UTF-8 filenames explicitly and the regression test checks the central-directory flag. This keeps names such as 旅行计划.txt, résumé-final.pdf, and ملف-عربي.txt intact when opened outside the browser.
03 — Next
NEXT_01 · FOLDERS
Add recursive folder selection, directory-aware collision checks, folder renaming, and ZIP output that preserves the source tree.
NEXT_02 · EXTENSIONS
Offer an explicit way to treat names such as archive.tar.gz as one compound extension while keeping dotfiles such as .env.local predictable.
NEXT_03 · COMPATIBILITY
Add a safe fallback for grapheme segmentation so filename operations remain usable when Intl.Segmenter is unavailable.
04 — Principles
WebRenamer separates shipped work from planned work. An item appears under Shipped only after it can be used in the public bulk file renamer workflow. Fixed items describe a user-visible problem and the behavior that changed. Next items are priorities, not promises or release dates.
The current release improves the path from batch rename preview to downloadable ZIP. The tool still processes selected files locally, so keep originals for important work and verify a representative set after export. For more focused workflows, use the PDF renamer or read the file renamer comparison.
Quick answers
It records user-visible file-renaming improvements, export fixes, compatibility work, and clearly marked next steps. Planned work is not presented as a released feature.
Invalid or conflicting destination names are excluded from the ZIP. Valid changed files and valid unchanged files are included, and the download button reports that exact export count.
The current browser workflow processes selected files locally and creates the ZIP in your browser. Keep backups of important originals and review the preview before exporting.