Voxalike Games

Creator Workshop

Upload a Mod to Workshop

Sign in, open Creator Workshop from your profile, choose Dub Mod or Judge Mod, upload a validated ZIP, complete the listing, and confirm you have permission to publish it.

Reviewed for v1.5.0Verified 2026-08-30

Check the current limits

  • Dub Mod ZIP: up to 800 MB
  • Judge Mod ZIP: up to 30 MB
  • Each audio clip: 60 seconds or less
  • Title: at least 5 characters
  • Dub description: at least 100 characters
  • Judge description: at least 60 characters

These limits were rechecked after the v1.5.0 notes and can change. Very large packs also require more browser memory and take longer to install, even though v1.5.0 improves long-Mod export reliability.

Upload and publish

  1. Sign in and open Creator Workshop. Select it from the profile menu in the upper-right corner.
  2. Choose the Mod type. Dub Mod is a playable scene; Judge Mod changes result presentation.
  3. Select the ZIP. Wait for validation and read any failure message before retrying.
  4. Complete the listing. Add a useful title, description, tags, correct spoken language, creator credit, and thumbnail or preview.
  5. Confirm rights and publish. Crediting someone does not replace permission to upload their work.

Understand account publication limits

Accounts younger than 7 days can currently publish 7 new Mods per rolling 24 hours. Accounts at least 7 days old can publish 20; approved Community Contributors can publish 50. Replacing an existing ZIP does not count as a new publication. An unfinished multipart upload can occupy a slot for up to two hours unless you cancel it.

Edit, replace, hide, or delete

Use My Mods in Creator Workshop. Edit Details changes listing text, language, tags, uploader visibility, and thumbnail. Public text fields cannot contain external links. Replace ZIP keeps the existing page, ratings, subscriptions, and download count, but v1.4.6 and later require an update note shown on Change Notes.

Hide removes a Mod from public Workshop and cancels subscriptions. Permanent deletion becomes available seven days after hiding. Test a replacement locally and describe what changed before uploading it.

Publish a useful listing

State what scene the pack contains, its language, approximate length, roles, content warnings when relevant, and what changed in a replacement. Do not split one work into artificial duplicates to inflate counts, and do not reuse another creator's work without permission.

Prepare the ZIP before you upload

A smooth Workshop upload starts before the browser picker opens. Keep the finished Mod in one clearly named folder, export a fresh ZIP from that folder, and avoid nesting a second ZIP inside it. Use a short file name that identifies the scene and version, such as scene-name-v2.zip, because the saved file name is often the first clue when collaborators compare builds. If the pack was edited on more than one computer, make one person responsible for the final archive so old images, unused audio, and draft metadata do not travel with the release.

Test the archive locally in Voxalike before publishing it. Import the same ZIP you plan to upload, not the source folder from your editor. Open the beginning, middle, and final prompt, record one disposable line, preview the result, and export a short test if the pack is large. This catches missing media, broken timing, silent clips, and browser memory problems while the file is still private. Keep a small release note beside the ZIP that names the source, spoken language, role count, approximate length, and any content warning you expect to show in the listing.

Understand validation failures

When validation fails, do not immediately rebuild the whole Mod. Read the message, change one condition, and upload again only after the local copy still works. File-size failures usually mean the archive includes unused video, duplicate audio, or a recording export that should not be part of the playable pack. Description failures mean the public listing is too short to explain what the player is downloading. A useful description names the scene, who speaks, what skill the pack practices, and what a player should check after import.

If a ZIP appears to upload forever, cancel the attempt before starting several new ones. An unfinished multipart upload can temporarily occupy an account publication slot, so repeated retries can make the account limit look stricter than it really is. Switch to a stable connection, close other upload-heavy tabs, and try a smaller test archive if the original is near the limit. For group projects, ask the person with the fastest connection to publish, then use Replace ZIP later if another teammate prepares a cleaner build.

Rights, credits, and moderation review

Workshop publishing is not only a technical step. The uploader should be able to explain why they are allowed to publish the material, where the source came from, and whether the pack uses copyrighted video, music, character art, or another creator's edit. Crediting a source is good practice, but credit by itself is not permission. If you cannot verify permission, keep the pack private, replace the media with original work, or link players to an official source instead of redistributing the material.

Use content warnings conservatively. Mark strong language, intense shouting, horror imagery, suggestive jokes, flashing visuals, or other material that could surprise players before they start recording. Do not hide warnings to make a pack look more broadly usable. Clear warnings help moderators, players, and rights holders understand the listing quickly, and they reduce the chance that the page looks like a thin download doorway with no editorial context.

Update an existing Mod responsibly

Use Replace ZIP when the pack is the same work with cleaner timing, corrected files, improved volume, or repaired prompts. Use a new Workshop entry when the scene, source, language, or role structure changed enough that subscriptions and ratings would describe the wrong thing. The update note should tell players what changed in practical terms: fixed silent prompt, replaced missing thumbnail, reduced file size, corrected language tag, or added final role. Avoid vague notes such as "minor fixes" when the update affects a player's recording session.

After replacement, open the public listing from a normal browser tab and confirm that the title, thumbnail, description, tags, download state, and change note all match the new ZIP. Then install it as a player would. A replacement that works in your editor but fails from the public listing still needs correction before you announce it to a room. Keep the previous ZIP for a few days, because it is the fastest way to compare a regression when a subscriber reports that a working pack broke after the update.

Sources and changes