For Developers
Advanced workflows for power users and developers. These steps are not officially supported and can lead to data loss. Back up your library first.
Manual folder import structure
You can prepare a folder on your computer and place it into the app storage.
Required structure:
- A folder named
UUID-*(must end with-*). - A card folder named
UUID-[]for each card. - Each card folder contains audio files and a
card.meta.
directory.meta (folder metadata)
The directory.meta file lives inside the folder and describes the folder itself. It is optional for import, but recommended.
Typical fields:
name: The folder name shown in the app.id: The folder id (oftenUUID-*).- Other optional fields the app can regenerate later.
If directory.meta is missing, the folder can still appear, and you can rename it in the app.
card.meta (card metadata)
Each card folder includes a card.meta file describing the card and the order of its audio sides.
Key fields:
name: Display name for the card.id: The card folder id (oftenUUID-[]).created: Unix timestamp in milliseconds.order: Array of audio filenames without extensions, in the order they should play.
Minimal card.meta example:
{
"name": "Untitled Card",
"id": "4bb3a59c-f3fa-4e01-af00-9660b64e0c30-[]",
"created": 1624965156329,
"order": [
"64272783-ab41-4ae2-ac54-e62b9ed319a0",
"89ada03c-dcc3-40ca-a7f1-ffa3fb4f1ae8"
]
}
The order values should match your audio filenames without extensions. Most common formats are supported (mp3, wav, m4a, ogg).
Where to place the folder
- iOS: iCloud Drive container used by the app, inside the
cardsfolder. - Android: App data container in the
cardsfolder.
If you are unsure, create a test folder in the app and inspect the folder layout to mirror it.
Caveats
- The app may rename or normalize files during indexing.
- Incorrect folder naming can cause folders not to appear.
- Always keep a backup before moving or replacing the
cardsdirectory.