Describe a problem — or just say what you want: "make it fullscreen on the TV," "cut the input lag," "set up player two." EmuDoctor finds the right settings, shows you the exact change, and applies it once you approve. No menu diving, ever.
Verified fix, or you don't pay. A visit is only charged once EmuDoctor has confirmed the fix actually worked — otherwise the visit goes back in your pocket, and anything it changed goes back the way it was.
Your GPU reports Vulkan 1.3 and the software renderer is doing the work on the CPU. One line. Snapshot taken before writing.
Fixing breakdowns is half the job. The other half is everything you'd normally dig through menus for — you say it, EmuDoctor shows the exact change, you approve it. That's the whole interaction.
Understood on your machine, instantly — quick changes like this don't even need the AI. Free, offline, done.
The AI picks the right levers — vsync, run-ahead, audio latency — and shows every line before one approval applies them.
Display, aspect, controller profile, per-game settings — configured, launched, and watched for the first minute.
Every change is snapshotted first. One ask puts the file back byte-for-byte, whenever you change your mind.
Somewhere between the wiki page that's three versions out of date, the forum thread that ends in "works on my machine," and the settings screen with forty toggles you've never heard of, the evening is gone and the game still stutters.
None of that is anyone's fault — these emulators are free, they're extraordinary, and the people who build them don't owe you a manual. But the knowledge that makes them work is scattered across a hundred posts. EmuDoctor already knows where it lives. You describe the problem; it does the digging.
It reads like a clinic because that's the safest shape for this: look first, explain the plan, get consent, then prove it worked.
It reads your emulators, GPU, display, and controller in seconds. You don't hunt for a single config file.
You get one plain answer: this line, in this file, changed to this. No forty toggles to guess at.
One press and it's done. Nothing changes until you say yes, and every change can be undone.
It launches the game and checks the fix held. If it didn't, you're not charged for the visit.
There is no command line for it to reach. It cannot type a command, download an installer, or improvise. It picks from a fixed list of guarded capabilities, and each one knows exactly which file it may touch and what shape the value must be.
If a repair needs something outside that list, EmuDoctor tells you what to do by hand instead of doing it. That's the trade we made on purpose.
You see the old line and the new line before anything is written. No hidden edits.
One deliberate hold applies the change, keyboard and controller accessible. Release aborts.
Every touched file is snapshotted first. One button puts your setup back exactly as it was.
Only the problem and the relevant settings ever leave, with home paths and secrets stripped out.
Manager-owned files are left alone, so the two never fight over your setup.
It will not find, fetch, name, or link them. Ask, and it declines and moves on.
A click is something you do by accident. A hold is something you decide. It is the only moment in EmuDoctor where a file changes, and it is deliberately the slowest second in the app.
You could — and you'd be starting where we started, the better part of five months ago. We build with AI too; that's not the moat. The moat is everything a general-purpose coding agent doesn't come with, because it took months of breaking our own setups to learn:
A general agent's power is arbitrary commands — which on your save files and configs is exactly the risk. EmuDoctor's model picks from a fixed registry of guarded capabilities, every write is previewed and fingerprinted, plans are one-use, and undo restores byte-for-byte. That containment layer is months of work before the first fix.
Five emulators, five config dialects: which files quote values and which don't, per-game override formats keyed by serial and CRC, which files EmuDeck or RetroDECK own and must never be touched. A fresh agent rediscovers each of these at 1 a.m., on your machine. Ours ships with them regression-tested.
A chat agent's "that should fix it" is a guess. EmuDoctor applies the change, reads it back, launches the game, and watches the session — and every verified fix feeds a shared brain, so the diagnosis you get tonight already learned from the last hundred machines. A chat session starts from zero every time.
The brain isn't a fresh experiment bolted onto an emulator app. It runs on the proprietary self-learning engine we built for SparkBox — an entirely separate product of ours, where months of real-world diagnosis work shaped how it fingerprints problems, weighs outcomes, and refuses to serve a fix until it has proven itself repeatedly. That engine came with us; the hours that made it smart are not something a fresh chat session can improvise.
Every visit that verifies is counted here, and so is every one that didn't. We publish the failures because the number means nothing without them.
No subscriptions. Nothing expires. The app is free and stays free — visits are a small pack of repairs that only get spent when a fix verifies.
The whole app, plus an AI check-up that tells you what's actually wrong.
One visit, one repair — charged when it works, not when it starts trying.
Pay one time, keep everything, forever. Locked in at today's price — it goes up later; yours doesn't.
Then you don't pay for it. A visit is only charged when the fix is verified working. If EmuDoctor can't solve it, it tells you what it ruled out and what it thinks the real blocker is — and puts back anything it changed.
No. Visits include the AI — buy a pack and it works. If you'd rather use your own key (OpenAI, or a compatible local model), that's the Supporter tier, and repairs run on your account instead of spending visits.
Not without showing you first. Every change appears as an exact before-and-after line, applies only after you approve it, and is snapshotted so one click puts it back. Undo also refuses to overwrite edits you made yourself afterward.
No, and it never will — that's a hard line. EmuDoctor doesn't download, copy, or help you find games, BIOS, firmware, or keys. It works with files you already lawfully have: it'll scan your folders, sort them out, and launch them.
The app itself, forever — browse any setting, and type quick changes in plain English ("turn off vsync in RetroArch") that are parsed on your machine, no AI involved. Plus a free AI check-up that names what's wrong and how many visits the repair takes. The repair itself is a visit.
Yes — SteamOS, plus Windows and Linux. Deck setups are a big part of why it exists: docked-versus-handheld display settings, controller layouts, per-game profiles. It also leaves EmuDeck-owned files alone, so the two don't fight.
You can, and it'll give you plausible advice about a machine it can't see. EmuDoctor reads your actual config files, your actual GPU, your actual controller — then makes the edit, launches the game, and checks whether it worked.
For AI repairs, yes — the reasoning happens at a model provider. Manual mode works offline. Your files stay on your machine either way; EmuDoctor sends only the problem and the relevant settings, with home paths and secrets stripped out.