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 · FOLDERS
Choose a folder, collect its files recursively, and keep the source directory tree in the exported ZIP. Collision checks now use complete relative paths instead of treating every file as if it came from one flat directory.
2026-08 · FILE CONTROL
Files can be sorted before numbering, excluded one at a time, or given a manual destination name without changing the rest of the batch. The preview and export use the same active file order and inclusion state.
2026-08 · WORKFLOW
Undo and redo now operate on rule-stack changes, individual rules can be disabled without being deleted, and custom rule combinations can be saved and restored from the workspace.
2026-08 · EXTENSIONS
Common multi-part extensions such as .tar.gz, .min.js, and .d.ts are treated as a complete extension during rename operations, while dotfiles continue to follow predictable filename rules.
2026-08 · METADATA BETA
Metadata is read locally on demand and can be used in rename templates. This first release covers common JPEG camera and capture-date fields, common ID3v2 music fields, and basic PDF document properties; broader variants remain on the roadmap.
02 — Fixed
FIX_01 · PATH COLLISIONS
Two files may share a filename when their relative directories differ. Validation and ZIP export now compare the full destination path, preventing silent replacement in multi-folder batches.
FIX_02 · PRODUCT CLAIMS
Product copy now distinguishes ZIP-exported copies from in-place disk changes, acknowledges browser and device memory limits, and no longer implies that administrator access is universally unnecessary.
FIX_03 · EXPORT
Valid unchanged files remain in the archive, rejected paths are excluded, multilingual filenames use explicit UTF-8 encoding, and the download action reports the exact number of exportable files.
03 — Next
NEXT_01 · DIRECTORIES
Plan folder entries explicitly so empty directories can survive export, folder path segments can be renamed, and files can be reorganized into new relative directories inside the ZIP. In-place disk operations are not part of the current release.
NEXT_02 · METADATA
Expand into common IPTC fields, optional EXIF GPS and dimensions, more ID3 versions and encodings, and a full PDF parser for compressed object streams. Encrypted PDFs will first receive clear password and unsupported-state reporting.
NEXT_03 · ADVANCED RULES
Evaluate insert-by-position, strip, randomize, padding, cleanup, transliteration maps, mapping input, rule import and export, and repeatable automation without promising unsafe filesystem access.
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 a directory-aware downloadable ZIP. It does not rename files or folders in place. Metadata support is an intentionally limited first release, so keep originals for important work and verify representative results after export. For a focused workflow, 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.