Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


If you have Anki media not syncing while cards arrive normally, investigate the media files and their transfer separately from the collection database. Preserve the working copy, identify one missing image or recording, and verify it on the receiving device before changing anything that could replace your notes.
Key Takeaways:
- Card synchronization and media synchronization have different completion checks.
- A missing file, an invalid reference, and an interrupted transfer need different repairs.
- Test one existing media item without deleting the media directory or forcing a collection download.
- Recovery means the receiving device can display or play that item after syncing.
Start on the device that still has the correct notes and playable media. Record its Anki version, profile, account, and the receiving device's version. Close unrelated editing sessions so that your investigation does not introduce new card changes while you compare synchronization results.
Export a collection backup with media included and keep it outside the working profile. Check the export options rather than assuming every automatic database backup contains your audio and pictures. Record where you saved the export, and keep the original files untouched until you have verified the receiving copy.
Choose one affected note and write down its deck, the relevant field, and a harmless media filename. For private study material, use a local worksheet rather than posting the card text or recording publicly. A short identifier is enough to follow the same item through each test.
The device diagnosis sequence helps if Anki is only one of several failing applications. This guide stays with Anki's collection and media objects. If several unrelated storage applications are also stuck, the direction-based cloud sync checks can help you separate local state from service-side trouble without repeating collection operations.
Open the selected note on both devices before syncing. The reference device must actually display the picture or play the sound; seeing its filename in a field is insufficient. If neither device has a working file, stop the network comparison and locate a backup or the original media source first.
Do not resolve an upload/download prompt by guessing which device is newer. A collection replacement can discard edits and is not a media repair. If both devices contain important unsynchronized changes, pause and plan their reconciliation before continuing.[1]
Run a normal sync on the reference device and observe the media portion of the operation. Let the task finish or produce a specific error before restarting it. Then sync the receiving device and compare the same note, not merely the total number of cards.
Anki merges media changes independently of a one-way collection sync. Choosing Upload or Download for the collection does not turn media into a matching one-way transfer. This distinction explains why a successful card operation does not prove every sound or image has arrived.[1]
Use this worksheet to identify the next branch:
| Observation | What it establishes | Next check |
|---|---|---|
| Note exists, referenced file is absent locally | Database content arrived without usable local media | Check transfer result and the source file |
| File exists but does not play on either device | Transfer may be irrelevant | Check the original file and its format |
| Source plays, receiver does not after sync | A device-specific or media-transfer issue remains | Compare filename, file presence, and playback |
| Media sync reports a connection error | A network branch is worth investigating | Record the error and preserve the same test item |
Record the start time, whether you left the app open, and the final message. A changing queue can indicate ongoing work rather than permanent failure. If you have a large collection, avoid repeatedly closing the client just because card synchronization finished quickly; media may still need attention.
Keep the exact error category, such as a connection failure or a file-related complaint, but remove account identifiers before sharing it. A generic “sync failed” recollection is less useful than the operation that failed. Do not assume a service outage from one computer's result; compare another permitted network or check official support information first.
Use Tools > Check Media to inspect missing references and unused files. Read the report without choosing deletion or emptying the trash. The purpose here is to locate the selected item, not to clean your entire collection while synchronization is uncertain.[2]
Match the reference to the real filename. A name displayed in HTML may contain encoded spaces or characters, so visual differences are not automatically a mismatch. Check the underlying filename carefully before renaming anything; a rename without updating the note can create a fresh broken reference.[2]
If media was added manually, review whether the file is physically present and compatible with the supported naming rules. A symbolic link that works on the desktop is not equivalent to a media file copied into the collection. The official media instructions describe these limitations; follow them for the single affected item rather than bulk-reorganizing the folder.[2]
Try the reference copy locally. If the file is damaged, changing the connection cannot repair its contents. If it plays on desktop but not on the receiving platform, check that platform's supported format before treating the problem as an interrupted download.
Do not delete files reported as unused merely to shrink the transfer. References in templates and special naming conventions need attention, and your current goal is recovery. Keep the report, the working file, and the export so that later cleanup remains a separate, deliberate task.
An edited file can also be a different case from an added or replaced file. Consult the synchronization instructions before assuming an in-place edit will be detected. Preserve the original and make any supported correction intentionally; do not continually rename files to provoke a sync without tracking which note references each version.[1]
Only enter this branch when the original file works, the reference is correct, and the media operation shows a connection problem. If you already use a VPN, disconnect it for a permitted baseline first. Keep Anki's profile, account, application version, and test item unchanged.
Anki's sync needs outbound HTTPS access, and its proxy behavior depends on platform and configuration. On a managed computer, ask the administrator to check the approved access rules. Do not disable certificate verification, paste proxy credentials into a public report, or remove organization settings to make a test pass.[1]
For Windows, review the system proxy ownership checks before toggling settings. Record whether a manual proxy, setup script, or management policy is involved. A browser opening AnkiWeb does not establish that Anki's own media requests use a working path.
With AethoVPN on the computer running Anki, connect to an available nearby location and enable global mode for the media-transfer comparison. Use Pro or Premium for desktop access: Windows uses the official installer, Debian/Ubuntu x64 uses the official .deb, and Mac uses the website setup guide with a VPN client and Pro or Premium. Repeat normal sync for the existing collection, then let the receiving device sync and try the selected media; do not replace or re-upload the whole collection for this test.
This changes the route, not the media reference, file format, account, or collection contents. If the same item still fails, disconnect and retain both results rather than cycling through many locations. For a new account needed to run this comparison, start the 3-day Pro trial; it is available once per user.
Use the connection comparison checklist to organize baseline and changed-route observations. An active VPN or a changed IP is preparation evidence, not Anki recovery. Respect local rules and network policy, and skip the comparison if the connection method is not authorized.
After the reference device's media sync completes, synchronize the receiver normally. Open the same note and reveal the side containing the image or audio. Display the image, press the actual playback control, and confirm you are testing the original item rather than a newly imported duplicate.
Keep a record of source playback, media-sync result, receiver playback, and the route used. If the receiver continues to report a transfer error, investigate that receiving connection separately. One computer's successful upload does not prove another device has successfully downloaded the result.
If the file is now present but playback fails, leave the network branch. Inspect device format support, the note reference, and local playback behavior. If the original file remains missing after completed media operations, send official support the versions, timestamps, sanitized error, and one filename, without sharing private notes or your collection export unless explicitly needed through a trusted channel.
Stop once the item displays or plays and a later normal sync does not reproduce the transfer error. Also stop if a protected account, certificate, managed-network, or missing-source-file issue appears: those are reasons to seek the responsible owner, not to force a different route. Restore temporary connection changes you no longer need and retain the backup until the normal workflow is dependable.
No. A forced collection upload or download changes database reconciliation, while media follows its own merge process. Preserve both devices' edits and investigate the media task instead.[1]
Card records and media files are separate synchronization objects. A note can therefore be available before its referenced image is usable on the receiving device; check the media result and local file.
Not during diagnosis. Read the report to locate missing references, preserve your working copy, and keep cleanup separate so you do not remove useful material while synchronization is uncertain.
Yes. Playback support can differ by platform. If the receiver has the file but cannot play it, check format support instead of repeating uploads or blaming the route.[2]
No. The receiving device must synchronize the existing media and display or play it. A connected tunnel, changed IP, or accessible web page cannot substitute for that result.
Use the same note, field, and filename recorded before troubleshooting. Sync both sides in order and test the original media on the receiver, without adding a duplicate note.
Provide both client versions, operating systems, the failed media operation, timestamps, a sanitized error, and a harmless filename. Keep account credentials, private recordings, and collection exports out of public posts.
This is an independently written guide, not an Anki project publication. The cover logo identifies Anki.
Sources checked 7 October 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.