Install from the Snap Store
Voxis is published on the snap stable channel. On any distribution where snapd is available, the install is a single command:
sudo snap install voxis
That is the whole install. There is no repository to add, no .deb to download and no build step — the snap ships the engine, its Python runtime and the GTK/WebKit stack the window is drawn with, so nothing already on your machine has to match a version we picked.
We deliberately do not print a version number on this page. Stable moves, and a number written into documentation goes stale the day after a release. To see exactly what the channel is serving right now, run snap info voxis and read the stable: line; to see what you actually have installed, run snap list voxis. Both of those are true at the moment you type them, which is more than a page can promise.
Updates arrive the way every snap does — snapd refreshes the package in the background, and sudo snap refresh voxis pulls one immediately if you would rather not wait. There is no in-app updater on this channel; the store is the update mechanism.
Connect the audio permission — without it the install is deaf
This is the one step that is easy to skip and impossible to work around. Snaps run under strict confinement: the package declares which interfaces it wants, and the system decides which of them are actually connected. Voxis needs the audio-record interface, because reading what your machine is playing goes through the same recording path as reading a microphone.
An install whose audio permission is not connected stays deaf. The app starts, the window opens, the language pickers work, a session appears to run — and no audio ever reaches the engine, so no translation ever comes back. It does not present itself as a permission error; it presents itself as silence. Connect it explicitly:
sudo snap connect voxis:audio-record
You can confirm the result before you start a session. snap connections voxis lists the package's interfaces; the audio-record row should name a plug and a slot rather than a dash in the connected column. If it shows a dash, the command above has not run, or it ran against a different install.
- Run
sudo snap install voxis. - Run
sudo snap connect voxis:audio-record. - Run
snap connections voxisand check that the audio-record row is connected. - Launch Voxis, sign in, and run the built-in sound test before you rely on a real session.
If you installed the package by hand from a local file rather than from the store, nothing is granted for you — the connect command is not an optional extra there, it is part of the install. Run it and re-launch the app.
How capture works on Linux: PipeWire and Voxis's own sink
The Linux side runs on PipeWire. Rather than trying to tap your speakers, Voxis creates a sink of its own, moves the audio of the apps you want translated onto it, and reads that sink's monitor. The translated voice it plays back goes to your normal output, so it never lands on the sink Voxis is listening to.
The practical consequence is the one that matters: Voxis does not re-translate its own voice. The separation is structural — the translated speech is simply not present on the stream being captured — rather than a filter that has to guess which sound is which after the fact.
It also means Voxis never takes over your system default output or your default input device. Your desktop keeps behaving the way it did before the app was installed, and quitting the app leaves nothing behind for you to undo.
Picking the source in a meeting app: "Monitor of Voxis_Virtual_Mic"
Two-way meeting mode has a second half: your own speech is translated and has to reach the other side. On Windows that means a virtual cable driver. On Linux, Voxis creates a separate sink for the outgoing leg, published under the name Voxis_Virtual_Mic, and plays the translated version of your voice into it.
Your conferencing app then has to be pointed at it. In Zoom, Teams, Meet or whatever you are using, open that app's own microphone selector and choose “Monitor of Voxis_Virtual_Mic” instead of your physical microphone. A sink's monitor is what other applications are able to record from, which is why you pick the monitor and not the sink itself.
What it is not: Voxis does not reach into your conferencing app and change that setting for you, and it does not switch your system default input to route you there automatically. You select the monitor yourself, in the meeting app, and you switch it back to your real microphone when the call ends. If you forget, the other side hears your untranslated voice — which is why the app raises a reminder at the start and the end of a two-way session.
Where transcripts are written
Transcripts are saved on your own machine, in your real home directory rather than inside the snap's private storage, so you can open, move and delete them with any file manager:
~/Documents/Voxis/Transcripts
If your desktop uses a localized or relocated Documents folder, Voxis follows the XDG setting instead of assuming an English path, so the folder lands where your system says Documents is. Each session gets its own subfolder, and any export you generate from the History view is written beside that session's record.
Reaching your real home requires the snap's home interface, which is normally connected on a store install. If transcripts are not where you expect them, check snap connections voxis for the home row the same way you checked audio-record.
Your account and your minutes work the same here
The Linux snap is not a separate product with separate billing. You sign in with the same Voxis account, and purchased minutes and the daily free allowance apply on the Linux snap as well — a pack bought on Windows is spendable on Linux, and the free daily allowance is that same allowance, not a second one running in parallel. Plans and balances are on Pricing.
There is no API key to paste and no key management to do on this channel: translation minutes come with the account, and the app fetches what it needs when a session starts.
Known limits of the Linux build
The honest list, so you can decide before you install rather than after:
- There is no AppImage package. Snap is the Linux packaging we publish; we are not shipping an AppImage alongside it.
- No automatic conferencing routing. The outgoing leg of a meeting is not wired into your conferencing app for you — you choose “Monitor of Voxis_Virtual_Mic” in that app's own microphone selector, and you set it back afterwards.
- Your system defaults are left alone. That is a design choice rather than a missing feature, but the consequence is real: the app will not repair a misrouted setup by taking over your default devices.
- A hand-installed local package starts with nothing connected. Interfaces that are granted on a store install have to be connected by hand there.
If a session stays silent
Silence on Linux almost always resolves to one of a small number of causes, and they are quick to separate from each other:
- Check the permission first:
snap connections voxis, theaudio-recordrow. An unconnected interface produces exactly this symptom, and nothing else will fix it. - Run the app's built-in sound test. Playback and capture are checked independently, so it tells you which of the two halves is quiet.
- Confirm something is actually playing. Voxis translates what your machine is playing — a paused video or a muted tab gives it nothing to work with.
- In a two-way meeting, look at the meeting app's own microphone selector. If it still names your physical microphone, the other side is hearing you untranslated.
- If it is still silent, send a report from inside the app. The report carries a scrubbed log that names which capture path was used, which is the part nobody can reconstruct from a description.
Symptom-by-symptom help for both platforms is on Troubleshooting, and the rest of the documentation is indexed under Documentation.