This page is an index, not a manual. It lists the articles that exist today, in four groups: getting started, using it, account and troubleshooting. Each entry says what the linked page covers, so you can skip the ones you do not need.
Two things worth knowing before you start reading. First, these documentation pages are written in English and Turkish today; several product pages exist in more languages than the docs do. Second, this index is deliberately short: we would rather publish a handful of pages that are current than thirty that quietly rot.
| If you want to… | Start here |
|---|---|
| Get the app on a Windows machine | Download |
| Get it on Linux | Install on Linux (snap) |
| Understand what happens to the sound | How it works |
| Work out why a session is silent | Audio setup checklist |
| Translate a call in both directions | Meetings & calls |
| Keep what was said | Transcript & history |
| Sort out minutes or a refund | Pricing · Refunds |
| Run it for a team | Enterprise admin guide |
Getting started
Install, first run, and getting audio into the app. If you have never run VoxisLive, these are worth reading in the order below. Most of what people call a setup problem turns out to be a question about the audio path, and the first articles here are the ones that explain it.
- Install on Windows — the download page lists the ways to get the Windows build and what each one is for.
- Install on Linux — install from the Snap Store, including the permission connections a snap needs before it can hear anything, which is the most common reason a fresh Linux install stays quiet.
- Your first session — How it works follows one sentence from the sound your computer is already playing, through speech detection on your own machine, to the translated voice in your headphones. Read it once and the settings stop looking arbitrary.
- Audio setup checklist — the checklist is what to walk through when captions appear but you hear nothing, when nothing appears at all, or when the app is listening to a different device than you thought.
Using it
You choose a scenario before you start a session, and the scenario decides what gets captured. These articles are grouped the same way, so pick the one that matches the thing in front of you.
Video and Game mode
One-way translation of whatever your machine is already playing — a video, a stream, a game, a podcast. The use-case index lists them all; the ones to start with are video, gaming, streaming and podcasts. If you are studying a language rather than consuming content, language learning covers reading the source line and the translation together.
Meeting mode
Two translations running at once: what the other side says, and what you say. Meetings & calls is the article to read first — it sets out which direction needs a virtual microphone and which does not, and it is explicit about the delay you should expect. Per-platform walkthroughs exist for Zoom, Microsoft Teams, Google Meet, WhatsApp and Discord. For calls under a confidentiality obligation, that article states plainly what is and is not being claimed.
The captions overlay
Captions overlay covers the caption window that stays above other windows: what it shows, what it deliberately leaves out, and how it behaves over a full-screen game or video.
Transcripts, history and summaries
Transcript & history covers where a session is saved on your own disk, how to find an old one again, and the export formats. Session summary covers the summary button — including the fact that pressing it is the step that sends transcript text anywhere, which is exactly why it is a button you press rather than something that happens on its own.
Term lists
Terms & glossary covers the list of names and words you can hand the engine before a session — product names, colleagues' names, domain jargon — and, just as usefully, when adding a term makes the result worse instead of better.
Voice gender and dubbing
Original-voice dubbing covers the voice the translation is spoken in, where the voice can follow the original speaker and where it cannot, and where a voice choice is available at all. Languages lists the target languages, and voice credits names each local voice and the licence it is used under.
Account
Minutes, payment, keys and team administration. None of this needs the app to be running.
- Minutes and the daily free allowance — Pricing explains how minutes are counted, what the free daily allowance covers, and what happens when it runs out while a session is live.
- Refunds — the refund page is the policy itself, not a summary of it.
- Bring your own key (BYOK) — BYOK setup walks through using your own provider key instead of ours, and licensing explains what the unlock is, and what it is not.
- Teams and organisations — Enterprise is the overview; the enterprise admin guide is the operational one, written for the person who actually has to add people and watch a shared pool of minutes.
- Your own account — Account for the signed-in view of your plan and balance.
Troubleshooting
Troubleshooting is the index for this category — start there rather than here. It is organised by symptom, because that is the shape a problem actually arrives in: no sound, no captions, the wrong device, a voice that stops mid-sentence.
Two neighbouring pages help with specific cases. The audio setup checklist is the one to run before anything else, because a large share of reports resolve to a capture or output device that was not the one the user had in mind. What happens on an outage describes how a session behaves when a translation provider degrades or goes down — useful when the app is clearly running but the translation is not arriving.
If none of it helps, the app has a Report a problem action that attaches a scrubbed log. That is far more useful to us than a description, because it shows which device was opened and where the audio stopped. You can also reach us through contact.
What is not here, and why
Two categories are missing on purpose. There is no presentation mode and no picture-in-picture settings set in this product, so there are no articles about either. If you arrived from a search result or a comparison table that said otherwise, that table was describing something else.
We would rather say that plainly than keep a documentation section for a feature that does not exist. The same rule governs the rest of this index: every heading above is backed by a capability that has shipped, and anything still being written is listed as missing below instead of linked as though it were live.
Still being written
This index is new and it is not finished. Articles we intend to add, and which do not exist yet, include a first-session walkthrough with screenshots, a page on the browser extension that goes past what the product page covers, and per-symptom troubleshooting pages broken out of the single troubleshooting index. Until they exist, they will not appear as links here.
In the meantime, three places carry information that has not been folded into documentation yet. The changelog records what changed in each release. The blog carries longer explanations of specific behaviour, such as why a translation arrives when it does. And the trust center answers where audio and text actually travel, which is the question most often asked of documentation that does not cover it.
How to read these pages
Every article here follows the same habit as the app itself: describe the mechanism, then state the limit. A page that explains what something does will also tell you the case where it does not work, because that is the part you need before you rely on it in a real meeting or a real recording session.
- Find the article by what you are trying to do, not by the feature name — the table near the top of this page is built for that.
- Read the limits section before the setup steps. If the limit rules out your case, the setup steps do not matter.
- If an article contradicts the app, the app is right and the article is stale — tell us and we will correct it.