Kanora
Kanora
Features02

Metadata you can trust

Metadata only becomes invisible when it is already right. Until then it is the difference between a library that feels considered and one that feels like a pile of files with cover art attached, which is why Kanora approaches editing as careful curation rather than quick cleanup.

What This Means

Track, album, and bulk editors with live previews, artwork comparison, library-aware suggestions, and deliberate metadata changes instead of invisible cleanup.

Demo · Metadata you can trustFocusee · ~75s

Recording brief

Select two or three albums, open the bulk editor, change a genre field, and show the live preview before confirming. Then open a single album, use artwork comparison to review and swap a cover. The point is the deliberateness — show that nothing changes without you seeing it first.

What It Is

Kanora already exposes the kinds of edits collectors actually make: correcting album-wide fields, adjusting disc and track numbering, cleaning up genre drift, comparing artwork before you replace it, and applying deliberate changes across a whole selection without guessing at what you meant.

The useful thing here is not just that the controls exist. It is that the app shows you the shape of the change before it lands, which reduces the quiet damage that often comes from bulk editors designed around speed alone.

Why It Matters

People with large libraries usually know the cost of bad metadata because they have already paid it somewhere else. Once artist names split, release types blur together, or artwork starts drifting from one pressing to another, browsing becomes less satisfying and the library stops feeling dependable.

A good editor does not need to be loud. It just needs to be exact, reversible in your head before you commit, and honest about what is fully solved versus what is still being finished.

Current Shape

The editing surface is already broad and practical, especially around album-level work, artwork maintenance, and bulk correction. The remaining job is to make sure those edits carry the same authority all the way back to the source files, because that is where trust becomes durable rather than cosmetic.