Shelfarr Roadmap
Shelfarr is built to be fast, safe, and boring in all the right ways. The roadmap follows real user pain: eliminate manual cleanup first, make reviews effortless, and keep the interface ruthlessly simple.
Now
High-impact improvements that keep renames safe and predictable.
Ordered regex rules for title / author to remove junk and normalize naming.
Launch a docs website with quick start, settings reference, and a clear roadmap.
Create a backup of your Shelfarr instance (import / export functionality).
Quickly set scan presets for common use cases, from scanner tool. Save your own presets.
Rewrite the Multi Part audiobook support to be more robust and reliable. Improve the results layout for multi-part books.
Improve the themes in Shelfarr to be more consistent, and be able to be previewed from Settings.
Add Inbox feature so users can review exceptions, manage file renames during or after a scan.
Updates to database driver to ensure better performance during error handling in a scan.
Improve the user experience for multi-part audiobooks in a scan.
Next
Power features with guardrails.
Limited EPUB support for renaming based on embedded metadata (similar to MP3/M4B).
Schedule a scan for 2am in the morning, weekly or monthly to keep things tidy without manual effort.
Later
Nice-to-haves once the core is rock solid.
Translation of the UI into multiple languages (start with Italian).
Trust Shelfarr to rename without review when confidence is high (with an undo option).
Derive author/series/title when metadata is missing (apply only when empty; include a preview/test panel).
Paste sample metadata and see transform/extraction results before running a scan.
More helpful “target exists” guidance and optional conflict-resolution workflows (never overwrite).
Shareable naming templates + common cleanup rules (opt-in, transparent).
Different templates/rules per library root without spinning up multiple instances.
Optional integrations beyond ABS (only if they improve accuracy without adding complexity).
Help shape the roadmap
The best feature requests include a real path example and the desired result.
What to include
- Example path(s) + what tags look like today
- What you want the new name/path to be
- Any tricky edge cases (series numbers, multi-author, subtitles)
Where to post
Open a GitHub issue and link any related files or screenshots: github.com/VacantlyCrushing/Shelfarr/issues
If you can, include a small sample (one folder) to reproduce.