If your Intel Mac already runs Vois, the practical question is not whether your current project disappears. It does not. Your installed version and local project files keep working. The change is about where new Vois work goes next: Apple Silicon Macs and Windows PCs.
We are making that focus so the local studio can improve where current hardware delivers the best experience. Your scripts, voices, timeline work, and exports remain yours to keep. New features and new releases will target Apple Silicon and Windows.
What is changing
New Vois releases no longer include a separate Intel Mac build. The Mac version now targets Apple Silicon, beginning with M1 machines, while Windows remains supported.
The change does not turn an installed Intel version off. It means that version becomes the version you keep. It will not receive new features, compatibility updates, or future release fixes.
What stays with your Intel installation
Your installed Vois application keeps working as it does now. Your project files, scripts, cloned voices, pronunciation decisions, and exports remain on your computer. The local-first workflow is helpful here: there is no remote project library you need to recover before you can keep working.
Back up the material that matters, particularly active projects and their approved exports. Keep a copy of the installer for the Intel version you use. Those are sensible project habits for any software version that is no longer receiving updates.
Why Apple Silicon and Windows are the focus
Apple Silicon enables GPU acceleration for faster local generation. It also gives the team one current Mac architecture to build, test, and troubleshoot. That smaller support surface leaves more time to improve the parts of Vois that creators use: script preparation, casting, local generation, review, mastering, and export.
Windows support is unchanged. The point is not to remove a workflow from people who use it. It is to concentrate new development on the platforms that can receive and test the current studio reliably.
Move a project when you are ready
There is no urgent migration date for an Intel user whose current version does the job. When you do move to an Apple Silicon Mac or a Windows PC, bring the project deliberately:
- Copy the active project files, scripts, approved pronunciation notes, and any custom voice material you are permitted to move.
- Install Vois on the supported computer and activate your access.
- Open a copy of the project first, then audition a short representative section before changing the production version.
- Verify any cloned voice permissions and review the new export before you resume publishing.
Keep an Intel workflow stable
If you remain on Intel, treat the installed version as a stable production environment. Avoid changing an active project on the only copy you have. Keep local backups of scripts, exports, pronunciation decisions, and any voice material you are permitted to retain. Before a major macOS update or a hardware move, open a copy of a representative project and confirm that the workflow still matches what you need.
For a client-facing series, note the Vois version used for approved exports alongside the script version and delivery settings. That small record makes future maintenance easier. You can explain which version produced an earlier chapter, locate the original source, and decide whether an update is safe to make on the Intel installation or should wait for a supported machine.
What a supported-platform move gives you
Moving to Apple Silicon or Windows is not just an installation task. It is a chance to test the next version of the local workflow with an active script, the voices you actually use, and the export destination that matters to you. Start with one copied project. Generate a short review candidate. Compare it against the prior approved version. Then move the wider production library when you are confident in the result.
That measured approach preserves the reason Vois is local in the first place: your work stays under your control while you decide when a production change is ready.
When you are ready to move or start a new installation, check supported local production features and Get started. Bring one active script first, confirm the workflow on the new computer, then carry the rest of your work across.
The Vois Team