- Voxalike make dub mods from a scene video, timed dialogue, character roles, and reference audio bundled into one package
- Nine official build stages take a pack from raw scene to a publishable Workshop mod
- Accurate line timestamps keep recorded takes synchronized with the final scene video
- Local test sessions catch broken lines and missing assets before you publish
- Judge Mods are separate — they restyle the result screen without changing dialogue or scoring
What Are Voxalike Dub Mods?
When you make Voxalike dub mods, you are building the playable content other performers record over. A Dub Mod is a structured package that turns a prepared video scene into a full dubbing session: it supplies the scene, the characters, the roles, and every line of dialogue the game assigns to players. Voxalike then combines each player's recorded takes with your scene so the finished dub plays back as one complete performance.
Because Voxalike is a free HTML5 browser game with no standalone client, your package must load cleanly inside the browser. That makes correct package structure and browser-compatible media the two make-or-break details for any creator. Follow the official Dub Mod maker guide alongside this walkthrough for the current format specifics.
Scene Video
- The visual backbone
- Final cut with a fixed duration
- Timing locked before dialogue work begins
Character Roles
- Who performs what
- Every speaking character defined
- Consistent identifiers across all lines
Dialogue and Captions
- The script
- Line text tied to characters
- Readable directly in-game while recording
Timing Data
- When lines appear
- Start and end timestamps
- Synced frame-accurately to the video
Dub Mods are often confused with Judge Mods, but they serve different purposes. Use this comparison before deciding which type of pack you want to build:
| Aspect | Dub Mod | Judge Mod |
|---|---|---|
| Core purpose | Defines playable scenes, roles, and lines | Restyles the judging screen |
| Main assets | Video, dialogue, timestamps, audio, artwork | Judge images, names, score labels, feedback, sounds |
| Supplies dialogue | Yes, every performed line | No |
| Changes scoring rules | No | No, presentation only |
| Judge slots | Not applicable | Four customizable slots |
| Workshop distribution | Yes | Yes |
A Dub Mod defines what players perform. A Judge Mod defines how the result screen looks and sounds. Neither type modifies Voxalike's underlying performance scoring.
Step-by-Step: Make Voxalike Dub Mods
The official creator flow breaks pack building into nine stages. Group them into five working phases and the project stays manageable from first cut to Workshop release.
Prepare the Scene and Characters
Finalize the scene video and lock its duration, then define every speaking character with consistent role identifiers. Any timing change after this point forces rework downstream, so treat the final cut as fixed before moving on.
Write Dialogue, Captions, and Timestamps
Enter the text players are expected to perform, attach each line to its character, and set start and end times that match the final video. Captions should track the spoken dialogue closely enough that players can record directly from the game.
Attach Audio Assets
Add reference line audio so players can hear how the original dialogue fits the scene before recording their own takes. If the scene benefits from music, include an optional backing track synchronized to run underneath the performances.
Add Metadata and Cover Art
Give the pack a title, complete its package metadata, and prepare a cover image that represents the scene. This information identifies the mod both inside Voxalike and in its Workshop listing.
Assemble, Test, and Publish
Place the video, audio, captions, timestamps, character data, metadata, and artwork into the required package structure. Run a full test session, fix anything that fails to load, then publish the tested pack to the Workshop.
For creators who prefer the full granular checklist, here is how the nine official stages map to requirements:
| Stage | Task | Key Requirement |
|---|---|---|
| 1 | Prepare scene video | Final duration matches dialogue timing |
| 2 | Create character roles | Consistent identifiers per character |
| 3 | Add dialogue and captions | Every line assigned to a character |
| 4 | Set line timestamps | Start and end times synced to video |
| 5 | Add reference line audio | Browser-compatible audio per line |
| 6 | Add metadata and cover art | Title, pack metadata, cover image |
| 7 | Optional backing track | Audio synchronized with the scene |
| 8 | Assemble and test | Valid structure, all assets load |
| 9 | Publish to Workshop | Tested package, complete metadata |
Finalize the scene video before writing any timestamp data. Re-cutting a scene after timing exists is the most common cause of misaligned dubs and forced rework.
Package Structure and Asset Requirements
A complete Dub Mod package combines required and optional assets. Missing any required item prevents the pack from loading correctly, so treat this table as your pre-flight inventory before every test run.
| Asset | Purpose | Required |
|---|---|---|
| Scene video | Visual scene players dub over | Yes |
| Dialogue text and captions | Lines players read and perform | Yes |
| Line timestamps | Controls when each line becomes active | Yes |
| Character role data | Maps lines to playable roles | Yes |
| Reference line audio | Original dialogue playback before takes | Yes, where used |
| Pack metadata and title | Identifies the mod in-game and on Workshop | Yes |
| Cover image | Listing artwork | Yes |
| Backing track | Music under recorded performances | Optional |
Two structural rules keep packages reliable. First, every dialogue line must resolve to a defined character role — orphaned lines break both Solo play and multiplayer line assignment. Second, timestamps must reference the final video duration, not an earlier edit, because the game activates each line based on that timing window.
Use browser-compatible audio and video formats throughout the package. Voxalike prepares and plays all content in the browser, so desktop-only formats can pass a quick file check yet fail during an actual session.
Test, Publish, and Update Your Mod
Testing comes before publishing, without exception. Load the assembled package in Voxalike and run a complete session: confirm every line appears at the right moment, every role receives its recordings, and every media file plays. Only a pack that survives a real session should reach the Voxalike Workshop.
Pre-Publish Checklist:
- Every line assigned to the correct character role
- Timestamps aligned with the final scene video
- Reference audio plays for each prepared line
- Metadata and cover image complete
- Full test session finished without load errors
Publishing requires three things: a tested playable package, complete Workshop-facing metadata, and cover artwork. After release, keep the Workshop version authoritative. When you ship an update, players update or reinstall their local browser copy so installed content matches your current version — a subscription tracks the item on their account, but each browser still needs its own working installation.
A pack that loads every line, role, and asset in a full test session is ready for the Workshop. Publish it, then monitor ratings and downloads to plan your next update.
Run Your Dub Mod in Multiplayer
Multiplayer rooms are built around the host's selected Dub Mod. The host creates a private room and shares the room code; the room then runs on the host's chosen content. Each player needs that mod available locally before the session can start correctly, and current versions of the game can automatically install the host's mod for joining players. If someone disconnects, they reconnect to the room using the group's room information and continue with the same mod installed.
| Detail | Value |
|---|---|
| Co-op player cap | Up to 12 players |
| PVP player cap | Up to 8 players |
| Room access | Private rooms with shareable codes |
| Session content | Host's selected Dub Mod |
| Line assignment | Round Robin or Claim Mode |
| Disconnect handling | Reconnect using room information |
Round Robin rotates lines automatically between participants, which suits quick party sessions. Claim Mode lets players pick the lines or roles they want, which works better when someone has their heart set on a specific character. Choose the mode that matches your group before recording begins.
Have everyone run Mic Check and confirm the host's Dub Mod is installed before Ready Up. Fixing input or content problems first keeps the session from stalling at launch.
Dub Mod Maker FAQ
Q: Do I need to install anything to make or play Voxalike dub mods?
No standalone client is required. Voxalike is a free HTML5 browser game, so both creating and playing Dub Mods happens in the browser. Follow the official package structure, and finished mods load directly in a supported browser.
Q: Can a Dub Mod change how judges score performances?
No. Judge Mods customize judge artwork, names, score labels, feedback lines, and reaction sounds across four slots, but they are presentation-only. Scoring rules stay the same regardless of which Dub Mod or Judge Mod is installed.
Q: Where do I publish a finished Dub Mod?
Publish to the Voxalike Workshop after testing. You need a tested playable package, complete Workshop-facing metadata, and cover artwork before the pack becomes discoverable to other players.
Q: Do all players need my Dub Mod installed in multiplayer?
Yes. Rooms run on the host's selected mod, so each player needs it available locally before Ready Up. Current versions can automatically install the host's mod for joining players, which removes most missing-content errors at session start.
Cross-check your package against the official creator documentation at voxalike.com/guide/make-dub-mods and follow release notes on the itch.io devlog for format changes introduced in updates such as v1.4.0.