01 — integrations · vaure pack

One file.
One tap.
Your music in Vaure.

Vaure Pack is a .vau file the user imports into the Vaure app with one tap on a link. Inside — tracks with cover art and metadata.

.vau · zip
https
one-tap import
album / playlist / library

02 — from files to a link

Four steps.

01

Build a ZIP

Tracks + manifest.json into an archive, rename to .vau.

02

Embed tags

Title, artist, album, cover — straight into every audio file.

03

Host over HTTPS

With Content-Length, ideally Range support. No interactive auth.

04

Build a link

Long link with percent-encoded URL — or a short one after registering with Vaure.

03 — anatomy of .vau

Just a ZIP, really.

my-album.vau
├── manifest.json
└── tracks/
    ├── 0F8A2C7E-….mp3
    └── 1B3D9F10-….m4a

Rename your .zip to .vau. manifest.json must sit at the root. Audio files — at the paths from the manifest. Any compression works, even STORE (audio is already compressed). Extra files are ignored.

MIME type application/vnd.vaure.pack

04 — manifest.json

The heart of the pack.

UTF-8 JSON at the root of the archive. Top-level fields describe the pack; tracks[] lists the tracks. Unknown keys are safely ignored.

createdAt — ISO-8601 with timezone, NO fractional seconds.

id — canonical UUID (case-insensitive).

storedFileName — path inside the ZIP, by convention tracks/<id>.<ext>.

05 — tags and covers

Metadata is read from the audio file itself.

On import Vaure reads title, artist, album and cover art from the file's tags (ID3, MP4 atoms, FLAC tags), NOT from the manifest. The title/artist/album fields in the manifest are only used for the import picker screen.

✕

A loose cover.jpg in the archive

Not read. Embed the cover into every track's tags (ID3 APIC and friends).

✓

Metadata inside the file

ID3 for MP3, atoms for M4A, tags for FLAC. Track number — TRCK in N/M form.

supported formats

MP3M4A (AAC/ALAC)FLACWAVAIFFCAF

OggVorbisOpus iOS can't decode — don't use.

06 — hosting .vau

The file has to arrive.

01

HTTPS with a valid cert

The inner URL must be https://.

02

Content-Length

Needed for download progress in the app.

03

HTTP Range preferred

Accept-Ranges: bytes — resilient on flaky networks.

04

Identified as a pack

Any of: .vau extension, Content-Type: application/vnd.vaure.pack, or Content-Disposition: attachment; filename="name.vau".

05

No interactive auth

If you need access control — bake a token into the URL itself.

07 — import link

Build a link.

Paste the full HTTPS address of your .vau — we'll percent-encode it into a Vaure import link. The long link works immediately, no approval needed.

your .vau URL

ready link

Want a short one?

A short link is . instead of the full URL. Vaure knows your host's base address and assembles the full path. To get a provider id — contact the Vaure team.

https://dl.vaure.app/i?url=1.aBcDeFgHiJkL Contact the team →

08 — pre-publish checklist

Eight items.

Progress below for your own use. Nothing is sent.

manifest.json at the archive root, valid JSON, all required fields.
exportKind is one of track / album / playlist / library.
createdAt — ISO-8601 with timezone, no fractional seconds; id — valid UUID.
Every storedFileName points to a file that actually exists in the ZIP.
Tags and cover are embedded in every audio file (not just in the manifest).
Audio in a supported format (MP3/M4A/FLAC/WAV/AIFF/CAF).
.vau is served over HTTPS with Content-Length, identified as a pack.
Long link built with percent-encoded url — or provider id obtained for short link.

0 / 8

09 — need help?

Talk to the team.

Provider registration for short links, non-standard formats, integration cases — all in @vaure_bot.

Open @vaure_bot ↗

One file.One tap.Your music in Vaure.