You can install a ready-made community pack in one click or import an original-format ZIP from your computer. This guide explains both paths and the checks that confirm a pack is really ready to play.
Use Community Packs when you want a curated archive that the site can download and parse for you. Use local import when you already have a ZIP or an extracted original-format folder. Both paths end in the same browser library, and neither path needs an account or a desktop installer.
Open Play, choose Community Packs, search or filter by type, then select a card. Read the title, creator, language, clip count, size, and content label before pressing Download & Install. The game shows download progress, parses the archive in memory, and stores the result locally. When it finishes, a Voice or Dub pack opens in the pack setup screen; host, judge, player, studio, menu, or chatter packs apply through Customize.
Open Pack Guides, Community Packs, or the pack setup screen and choose Import or Upload Your Pack. In the local import dialog, choose ZIP and select one .zip file. The importer accepts the original community format, detects one pack or a compilation, and reports when the pack is ready. Pack files are read in memory before they are saved to this browser.
If an archive tool created a folder rather than a ZIP, choose folder and select the unpacked directory. Keep the original root names and file extensions intact. A Voice Pack needs at least one WAV, MP3, or OGG clip; a Dub Pack also needs compatible scene media and its timing metadata. The folder path itself is not uploaded.
Check the detected pack title and creator, then inspect the clip count, captions, artwork, and the first playable line. For a Voice Pack, open Standard Gameshow and play the reference clip before recording. For a Dub Pack, open Dub Mode and confirm the video, captions, and cue order. This catches a bad archive before it interrupts a group session.
“No WAV, MP3, or OGG clips were found” means the selected root has no supported playable audio. A wrong title usually means the pack metadata is missing or nested one folder too deep. Re-export a clean ZIP with one clear pack root, remove editor caches and duplicate basenames, and import the new file. If a catalog download fails, retry once on a stable connection and report the pack title rather than repeatedly clicking.
Local imports are read in the browser before they are stored in IndexedDB. Recordings stay local unless you explicitly save or share a result. Clear the site data or remove a pack from the in-game library when you want to clean up local storage.
Before a shared session, install the pack, play one reference line through your speakers or headphones, check the selected microphone, and confirm that the next line loads after a judge reveal. Keep the original ZIP as a backup, write down the pack creator and version, and remove an old duplicate before reinstalling an updated archive.
Yes. Curated downloads and local ZIP imports work in the browser without an account.
The parsed pack is stored in this browser’s IndexedDB and remains available on the same site until you remove site data or delete the pack.
The archive may contain only customization assets, a nested root the importer cannot identify, or no supported WAV, MP3, or OGG clips. Reopen the ZIP and check its root structure.
Yes. Choose the local import folder option and select the extracted original-format pack directory.
Import the updated ZIP or install the newer catalog version. The game replaces an existing pack with the same normalized type, title, and creator identity.