Auzi

An opinionated local desktop music manager and player built with Avalonia and .NET.

Auzi is for people who manage and play music files they already own. It is not a discovery app, streaming client, music store, podcast platform, social feed, or cloud library service.

Features

• Build a local music library from your existing files and folders, with import and duplicate/alternate-format detection.
• Browse, search, sort, and play tracks by library, album, artist, static playlist, or smart playlist.
• Edit track metadata, artwork, ratings, and sentiment for one track or many tracks at once.
• Create static playlists, generate artist playlists, and define smart playlists from rule-based filters.
• Audit and auto-fix metadata issues, organize files by metadata, and clean unwanted tag fields.
• Combines matching FLAC, MP3, and bitrate variants into one playable library track.
• Plays the best source by default and keeps metadata synced across all linked files.
• Reuse the same music folder across macOS, Linux, and Windows installs, including multi-boot setups.
• Pair with a companion iOS app over local mDNS/HTTPS to sync selected music and receive playback history or feedback updates.
• Choose from a variety of dark and light mode themes.

Screenshots

Theme: Sonic Glaze (Light)

Theme: VS Code 2026 (Dark)

Theme: Dracula (Dark)

Quick Installation

Use an existing installer when you want the easiest path to running Auzi.

Platform	Installer	Status
Linux	--	--
macOS	Mac App Store	Pending
Windows	Microsoft Store	Available

Building From Source

Build from source when you want to develop Auzi, inspect or modify the code, or run a local build instead of an app-store installer.

Requirements

• .NET 10 SDK
• Linux, macOS, or Windows

Run Locally

dotnet restore
dotnet build Auzi.slnx
dotnet run --project src/Auzi.Desktop

On first launch, choose your music folder. Auzi stores its database at <music folder>/.auzi/auzi.db.

Library Operations

Operation	Purpose
Scan for New Files	Discover tracks in the current music folder that are not already in the library and offer to import them
Import	Add files/folders to the library with duplicate detection
View Metadata Issues	Audit the library for metadata problems and offer fixes
Clean Tags	Eliminate most tag types/fields, keeping only essentials (ID3v2 for MP3, Xiph for FLAC)
Organize Files	Move and rename files into a cleaner folder layout based on metadata
Devices	Pair and manage companion devices, including sync source assignments

Local Data and Privacy

Auzi stores library data in a local database inside the selected music folder. This includes track records, file paths, playlists, metadata state, app-managed ratings or sentiment, paired-device state, and playback history.

File paths are stored relative to the selected music folder, so the same library can be opened from different operating systems even when that folder is mounted at different root paths.

Playback history stays in the local library database. Auzi records listening events and scrobble-qualified plays for future features such as year-in-review reports or a listening-history view. Scrobble qualification follows the Last.fm Scrobbling 2.0 threshold: after the 30-second minimum, a play qualifies once at least half the track or 4 minutes has played, whichever comes first.

When device sync is enabled, paired companion devices can send playback history or feedback updates back to the local Auzi database over the local-network connection. Auzi does not send scrobbles, usage data, playback history, or library information to the author or any cloud service.

Because music metadata, file paths, and listening history can still be sensitive, treat <music folder>/.auzi/auzi.db as private local app data.

Important Safety Notes

File Changes

Use Auzi at your own risk. While the application is intended to handle your music library safely, some operations modify audio files, including file names, folder layout, and metadata.

The author is not responsible for any loss, corruption, deletion, metadata damage, or other issues affecting your audio files, library, system, or other data. This includes cases where the application might unexpectedly delete files, move or rename them incorrectly, or mangle metadata.

None of that behavior is expected, but an abundance of caution is strongly recommended. Back up your music library before using Auzi.

Device Sync

When device sync is enabled, the Devices feature starts a local-network HTTPS sync server so companion devices can pair and download selected music. Pairing is initiated by scanning a QR code that contains the local connection details, TLS pin, and a short-lived 6-digit pairing code. Paired devices use bearer-token authentication after pairing, but the pairing endpoint is intentionally reachable without an existing token.

Only enable device sync on networks you trust, only scan pairing QR codes with devices you control, and remove paired devices you no longer use.

Metadata Policy

Auzi keeps music metadata deliberately small and predictable. When it writes tags, it preserves only title, artist, album, album artist, year, track number, track count, disc number, disc count, and one artwork image.

All other tag fields are removed, including but not limited to comments, lyrics, genres, grouping fields, custom frames, and embedded extras from other music managers. This is intentional: Auzi treats tag cleanup as normalization, not as lossless metadata preservation.

License

Auzi's source code and bundled project assets are licensed under the MIT License. See LICENSE for the full license text.

That license does not apply to music files, artwork, metadata, playlists, libraries, or other content that users manage with Auzi.

Third-party dependencies and assets remain under their own licenses. See THIRD-PARTY-NOTICES.md for attribution and notices, with bundled license texts in licenses.