AMBOSS's Anki support is not identical on every device. As documented on 6 September 2026, pop-up explanations are supported in AnkiMobile on iPhone and iPad and in AnkiDroid on Android. Features connecting Anki with the AMBOSS Qbank remain desktop-only in the dedicated product guidance.
That distinction resolves much of the confusion. Seeing a definition on an iPad does not mean the full desktop add-on has been installed there, or that every question-bank and deck-selection control should appear.
Separate the three connections
The AMBOSS Anki page checked on 6 September 2026 describes explanations within cards, question-bank recommendations from cards and matching AnKing cards for Qbank questions. These are related but different functions.
| Task | Desktop Anki | AnkiMobile on iOS | AnkiDroid on Android |
|---|---|---|---|
| AMBOSS term explanations | Supported | Supported with mobile setup | Supported with mobile setup |
| Full card-to-Qbank workflow | Desktop feature | Do not assume parity | Do not assume parity |
| Matching AnKing card workflow | Requires relevant deck and desktop workflow | Not a full desktop substitute | Not a full desktop substitute |
The table reflects the dedicated documentation, not a hands-on device test. Check it against current support information when setting up a new version.
Establish a working desktop installation first
The product page gives the desktop add-on identifier as 1044112126. Install through Anki's add-on controls and follow the current compatibility guidance rather than relying on an old tutorial for a different Anki release.
Confirm that the add-on works on a simple card before adding mobile synchronisation to the problem. Check that the correct AMBOSS account has access and that an explanation opens as expected. If desktop access already fails, changing settings on the iPad is unlikely to resolve the underlying account or installation issue.
Keep a backup before making substantial changes to a valuable collection. A study system containing months of edits deserves more care than a disposable test deck.
Enable mobile support, then synchronise both ends
The mobile-support instructions checked on 6 September 2026 describe enabling mobile support in the AMBOSS settings within desktop Anki, saving and synchronising devices through AnkiWeb. Active AMBOSS access and the appropriate mobile Anki app are required.
The order matters as a troubleshooting strategy. Make the desktop change, complete its synchronisation, then synchronise the mobile device. Check one recognisable card before assuming the entire collection is ready.
AnkiWeb is the bridge between collections, not another name for AMBOSS membership. According to the Anki synchronisation manual checked on 6 September 2026, an initial or forced one-way synchronisation requires choosing which collection to keep. Do not click upload or download at random when both devices contain important changes.
A useful iPad workflow does not require desktop parity
Imagine a fictional student who reviews cards on an iPad during a commute and does longer question sessions on a laptop in the evening. The mobile device can support brief retrieval and clarification, while the desktop remains the place for the fuller question-bank connection.
If a card reveals uncertainty, note the concept rather than abandoning the whole review session to rebuild the study system. Later, use a relevant question to check whether the learner can apply the distinction outside the flashcard's familiar wording.
That division of labour is a suggested workflow, not a claim that AMBOSS automatically schedules every deferred question. It can be effective without requiring every device to expose every feature.
Android support means AnkiDroid, not any flashcard app
A similarly named application is not necessarily the application covered by the instructions. Establish the actual app and account before troubleshooting the add-on.
If the card collection appears but AMBOSS explanations do not, check mobile support, completed synchronisation and current access. If neither the collection nor recent edits appear, solve the collection-synchronisation problem first.
Work through one issue at a time. Reinstalling several apps, changing accounts and forcing a full synchronisation together makes it difficult to know what changed and can put local edits at risk.
For unresolved problems, send support the device, operating system, Anki version, add-on version and a non-sensitive example. Do not include patient details or a large copyrighted deck when a minimal test card can demonstrate the issue.
Matching AnKing cards is a specific feature
A link between an AMBOSS question and AnKing material does not imply that the system can locate an equivalent card in every personal deck. The product documentation specifies the relevant AnKing deck for that matching workflow.
This matters when a learner has extensively edited or assembled a personal collection. A missing match may reflect the collection being used, not a missing medical topic or a failure of the question bank.
Treat suggested cards as candidates for learning, not an instruction to activate everything. Select material that addresses the actual error. A large addition to the review queue can consume time without resolving the misconception that prompted the search.
Explain first, then return to retrieval
A definition is useful when a term blocks understanding. It is less useful as a permanent substitute for attempting the card. Commit to an answer before opening supporting material whenever the purpose is retrieval practice.
If the explanation still leaves a gap, write down the question the card does not answer. For example: what distinction changes the diagnosis, or why does the same finding have a different significance in another context? That question is often more educationally useful than repeatedly revealing the back of the card.
This guide is published by iatroX and includes its learning tools as a separate option. Under September 2026 product information, iatroX's Socratic Tutor works from attempted questions and targeted follow-ups. It is not an AMBOSS add-on, an Anki synchronisation service or a promised automatic deck exporter.
For a committed Anki user, AMBOSS's documented integration may be a good fit. For a learner who needs to discuss the reasoning behind an error, guided tutoring may address a different need. The best setup is the one that supports a sustainable learning routine on the devices actually used.
Frequently asked questions
Can the full desktop AMBOSS add-on run on an iPad?
No. Use the device-specific setup and distinguish mobile explanations from the desktop Qbank workflow described above.
Why do my cards synchronise but the explanations do not appear?
Check that mobile support is enabled in desktop AMBOSS settings, both devices have synchronised and the account has active access. These are separate from simply having the cards on the device.
Does AnKing matching work with every personal deck?
The advertised matching workflow requires the relevant AnKing deck. Do not assume identical matching for an unrelated or extensively modified collection.