Voicemod V3 doesn't automatically import V2 sounds — you need to copy the files manually

When you install Voicemod V3, your old V2 custom voice packs and sound files stay in the V2 folder on your computer. V3 looks in a different location, so it won't see them unless you move the files there yourself. The process takes about five minutes and requires you to navigate two folders and copy a single directory.

The key difference is that V2 and V3 store sounds in separate places. V2 uses one folder structure, V3 uses another. Both versions can run on the same computer without conflict, but they don't share a library. If you want your custom sounds available in V3, you're moving files, not upgrading them.

Key Takeaways

  • V2 and V3 store custom sounds in different folders, so V3 won't see your V2 packs unless you copy them manually.
  • Your V2 custom sounds live in a "Voicemod" folder inside your user profile, and V3 looks for them in a "Voicemod" folder in a different location.
  • You copy the entire "CustomVoicePacks" folder from V2's location to V3's location, which preserves all your custom files at once.
  • After copying, restart Voicemod V3 completely and your imported sounds will appear in the voice list.

Where V2 stores your custom sounds

On Windows, V2 keeps custom voice packs in this location: C:\Users\[YourUsername]\AppData\Local\Voicemod\Voicemod\CustomVoicePacks. Replace [YourUsername] with your actual Windows username. If you're on Mac, the path is ~/Library/process Support/Voicemod/CustomVoicePacks.

The AppData folder is hidden by default on Windows, so you need to show hidden files first. Open File Explorer, click the View tab at the top, then check the box labeled "Hidden items". Now you can navigate to AppData and find the Voicemod folder inside it.

If you've never created custom sounds in V2, this folder might be empty or might not exist yet. That's fine — it means there's nothing to import. If you do have custom packs, you'll see folders inside CustomVoicePacks with names you gave them.

Where V3 expects to find imported sounds

V3 looks for custom sounds in a different location. On Windows, that's C:\Users\[YourUsername]\AppData\Roaming\Voicemod\CustomVoicePacks. Notice the difference: V2 uses "Local", V3 uses "Roaming". Both are in AppData, but in different subfolders.

On Mac, V3 uses the same path as V2, so if you're on Mac you may not need to do anything — V3 might already see your V2 sounds. Open V3 and check your voice list. If your custom packs are there, you're done. If not, follow the copy steps below.

The Roaming folder is also hidden on Windows, so use the same View tab method to show hidden items before you navigate there.

How to copy your V2 sounds to V3

Open File Explorer and navigate to C:\Users\[YourUsername]\AppData\Local\Voicemod\Voicemod. You should see a folder called "CustomVoicePacks". Right-click it and select "Copy".

Now navigate to C:\Users\[YourUsername]\AppData\Roaming\Voicemod. If a "CustomVoicePacks" folder already exists here, you have two choices: right-click it and select "Delete" to replace it entirely with your V2 version, or open it and paste your V2 packs inside to merge them. Most people prefer to delete and replace, which ensures V3 uses exactly what V2 had.

Right-click in the empty Roaming\Voicemod folder and select "Paste". Wait for the copy to finish — if you have many custom packs, this might take a minute. Once it's done, close File Explorer.

Restart V3 and verify your sounds imported

Close Voicemod V3 completely if it's running. Don't just minimize it — actually quit the process. On Windows, right-click the Voicemod icon in your system tray (bottom right corner) and select "Exit". On Mac, click Voicemod in the menu bar and select "Quit Voicemod".

Wait 10 seconds, then open Voicemod V3 again. Go to the voice list and scroll through it. Your custom packs should now appear alongside the built-in voices. If you don't see them, the copy didn't work — go back and check that you pasted into the Roaming folder, not the Local folder.

If a custom pack appears but sounds broken or won't load, the file might be corrupted or incompatible with V3. V3 uses a slightly different audio format in some cases. Try deleting that one pack from the Roaming folder and see if the others work. You can always re-create the broken one in V3.

What happens if you have both V2 and V3 installed

You can run V2 and V3 at the same time on the same computer without problems. They use different folders, so they won't interfere with each other. If you're still using V2 for streaming or recording, you can keep it installed while you test V3.

However, if you edit a custom sound in V2 after you've copied it to V3, the V3 version won't update automatically. You'd need to copy the updated file from V2's folder to V3's folder again. For this reason, once you're comfortable with V3, it's cleaner to uninstall V2 and do all your custom work in V3 going forward.

Troubleshooting sounds that don't appear after import

If you copied the CustomVoicePacks folder but your sounds still don't show up in V3, check three things. First, make sure you restarted V3 completely — a restart is required for V3 to re-scan the folder. Second, verify you pasted into the Roaming folder, not the Local folder. Third, open the Roaming\Voicemod\CustomVoicePacks folder and confirm the files are actually there.

If the files are there but V3 still doesn't see them, the pack might use a file format V3 doesn't support. V2 accepted some audio formats that V3 dropped. In that case, you'll need to re-create the sound in V3 using the V3 voice editor, or convert the audio file to a format V3 recognizes (usually WAV or MP3).

If nothing appears and the CustomVoicePacks folder is empty, you may not have had custom sounds in V2 to begin with. Check your V2 installation one more time by opening V2 itself and looking at its voice list — if you don't see custom packs there, there's nothing to import.

Frequently Asked Questions

Do I lose my V2 sounds when I install V3?

No. V2 and V3 are separate installations, and V2's files stay in the V2 folder. Installing V3 doesn't touch V2. Your V2 sounds remain in the Local\Voicemod folder whether or not you ever copy them to V3.

Can I use V2 and V3 at the same time?

Yes, both can be installed and running on the same computer. They use different folders and don't interfere. However, only one can be active in your streaming or recording software at a time, since both try to use your microphone.

What if I don't see the AppData folder?

AppData is hidden by default on Windows. Open File Explorer, click View at the top, and check "Hidden items". Now you can see AppData. On Mac, press Command+Shift+Period to show hidden folders in Finder.

Will my V2 sounds work exactly the same in V3?

Most will, but V3 has a different audio engine than V2, so some custom packs may sound slightly different. A few older V2 packs might not load at all if they use formats V3 dropped. Test your most important sounds after importing to make sure they sound right.

Can I delete V2 after I import my sounds to V3?

Yes. Once your sounds are copied to V3's folder, V2 is no longer needed. You can uninstall V2 without affecting V3 or your imported sounds. Just make sure the copy was successful and V3 shows all your custom packs before you uninstall V2.