Metlivi Blog

How to Bulk-Import and Organize a Personal RPG Audio Library

To bulk-import audio for tabletop roleplaying, first collect the files in a stable folder, sort and label them by how you will use them, then import one small batch into your chosen player or virtual tabletop. Check the results before importing the rest. This workflow helps you find ambience, music, and sound effects during play without turning the library into one long, hard-to-navigate playlist.

October 15, 20266 min readBy Metlivi Editorial Team
Section 1

Decide where you’ll play the audio

Choose the destination before moving files. A desktop audio player can hold a searchable personal library; a virtual tabletop (VTT) can put campaign playlists beside scenes and game materials; an RPG soundboard may offer quick access to individual cues. You can keep a master collection on your computer and copy only session-ready files into a VTT or soundboard when needed.

Check the destination’s supported formats and import behavior. Foundry Virtual Tabletop, for example, accepts audio formats including MP3, OGG, FLAC, WAV, WebM, and Opus. Its playlist editor can bulk-import valid audio files from a selected folder and assign basic names that you can edit afterward. The import creates playlist entries; it does not automatically supply useful scene labels. Foundry’s Playlists guide

Section 2

Stage a master folder before importing

Make one clearly named folder for the collection, then gather files into a temporary To Sort folder inside it. Keep the source folders until you’ve checked the imported batch. This gives you a known starting point and makes it easier to identify which files were included if an import misses something.

Use a small number of top-level categories that match play: Ambience, Music, and SFX (short sound effects). Under those, group by use or setting—such as Forest, Tavern, Travel, or Combat. Add campaign-specific folders only when those files truly belong to one campaign. These category names are a practical suggestion, not a standard; choose terms you can remember quickly at the table.

Section 3

Clean up names in batches

Replace vague source names such as track_07 with searchable labels that put the cue first: Forest_Rain_Loop, Tavern_Crowd_Loop, or Door_Stone_Open. Include a campaign or scene prefix only when it helps distinguish similar files. Keep names short enough to scan in your destination’s playlist panel.

If you use a tag editor, work on a copied batch and preview the changes before applying them. Mp3tag can import tags from file and folder names, rename files using tag fields, and apply repeatable action groups to selected files. Mp3tag’s converters guide Mp3tag’s actions guide Avoid applying one filename pattern to a mixed folder unless every file follows it: a pattern that fits one provider’s names can create incorrect tags for another group.

For RPG audio, useful descriptive fields might include title, category, setting, and intended use. Treat these as your own labels. Metadata support differs across formats: Mp3tag’s supported-format reference, for example, lists different tag systems for MP3, FLAC, OGG, WAV, and other formats. If a tag does not appear in your playback tool, put the most important search terms in the filename as well. Mp3tag’s supported formats

Section 4

Build playlists around table actions

Organize playlists around what you need to do in a scene, not simply around where a file came from. A Travel – Forest playlist can collect several ambience options; a Tavern playlist might separate continuous room sound from one-shot cues such as a door opening. Keep recurring ambience distinct from one-shot effects so you don’t accidentally start a single event as a long-running background track.

In Foundry, playlists can play sequentially, shuffle, play sounds simultaneously, or act as a soundboard for individual tracks. The guide also supports playlists nested in folders, descriptions, repeat settings, and per-track volume controls. Use sequential or shuffle playback for a collection intended to run as a playlist; use soundboard-only behavior when you want to trigger cues individually. Foundry’s Playlists guide

Section 5

Import a pilot batch, then scale up

Start with one category folder or a small campaign set. In the target tool, create the playlist first, then use its bulk-import or folder-import option if available. Foundry’s bulk import is available in playlist configuration and creates a sound for each valid audio file it detects in the selected folder. The track names can be edited afterward. Other tools may import differently, so confirm whether they copy files, reference their current paths, or make playlist entries before committing the full collection.

After the pilot import, compare the playlist against the source folder: check the number of entries, open a few tracks, confirm their labels, and verify that loops and one-shots behave as intended. If the destination groups everything under an unhelpful default name, rename entries or improve filenames before importing another batch. Fix the process once, then repeat it by category rather than repairing a large, mixed library later.

Section 6

Check formats, size, and playback

A file appearing in a playlist does not guarantee that it will play correctly in your session setup. Test files in the actual destination, especially if the library mixes formats or unusually large audio files. Foundry’s media guide notes that bitrate affects the balance between file size, streaming smoothness, and audio quality; it gives 128 kbps as a minimum recommendation and 192 kbps as a suggested maximum for its use case. Treat that as Foundry-specific guidance, not a universal target for every player or every sound. Foundry’s Media Optimization Guide

Listen to a few seconds of each imported file and check that the start is clean, the volume is usable, and the file plays for as long as expected. For loops, check the transition where the track restarts; Foundry notes that its repeat behavior may include a short gap. If a particular file fails, isolate it and check the extension and playback support before changing or converting the entire collection.

Section 7

Keep the library recoverable

Once the pilot works, move or copy files into their final folders and import the remaining categories in manageable batches. If the software offers playlist export, save an export alongside your session notes or library backup. Foundry allows playlist data to be exported as JSON, but treat that as playlist data rather than a complete audio backup: keep the actual audio files too. Foundry’s Playlists guide

Before a session, search for the cues you expect to use and test the important playlists. When a file goes missing, check whether its folder was moved or renamed and whether the destination still points to that location. Keep filenames meaningful, descriptions brief, and categories consistent as the collection grows; these habits make the next import easier and help you find the right sound when the table needs it.

Section 8

Sources

Related reading

Keep exploring this topic