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.

Heads up: These road map items are not deadlines. Want something bumped up? Log a feature request on our Discord with as much specific detail as you can!

Now

High-impact improvements that keep renames safe and predictable.

Apply Regex Templates
Shipped in v0.61
shipped

Ordered regex rules for title / author to remove junk and normalize naming.

Shelfarr.app Documentation
Shipped in v0.61
shipped

Launch a docs website with quick start, settings reference, and a clear roadmap.

Manual Review Improvements
In progress
in progress

Make manual review faster: fewer clicks, clearer warnings, smarter grouping.

Next

Power features with guardrails.

Scheduled Scans
Planned
planned

Schedule a scan for 2am in the morning, weekly or monthly to keep things tidy without manual effort.

Translation
Planned
planned

Translation of the UI into multiple languages (start with Italian).

Magic Mode
Planned
planned

Trust Shelfarr to rename without review when confidence is high (with an undo option).

Regex extraction (missing tags)
Planned
planned

Derive author/series/title when metadata is missing (apply only when empty; include a preview/test panel).

Rule testing in UI
Planned
planned

Paste sample metadata and see transform/extraction results before running a scan.

Better conflict handling
Planned
planned

More helpful “target exists” guidance and optional conflict-resolution workflows (never overwrite).

Later

Nice-to-haves once the core is rock solid.

Preset templates & rule packs
Idea
idea

Shareable naming templates + common cleanup rules (opt-in, transparent).

Per-folder settings
Idea
idea

Different templates/rules per library root without spinning up multiple instances.

More metadata sources
Idea
idea

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.