Repeto vs Anki: Features, Tradeoffs, and Verdict

Choose Anki if you need a proven flashcard system today, want deep control over note types and scheduling, or depend on local files, add-ons, and a mature multi-platform ecosystem. Consider Repeto after its 2.2 release if your main problem is turning material into editable card drafts while keeping FSRS and Anki package portability in the workflow; that Repeto update is still in preparation, so it is not yet the safer choice for an immediate switch.

Disclosure: Repeto publishes this comparison. We have a commercial interest in the decision. We link to first-party product sources, state where each tool is stronger, and separate currently available features from planned or pre-release ones. Facts were checked on August 21, 2026.

This page compares Repeto with the Anki ecosystem centered on the open-source desktop app, including AnkiWeb, the official AnkiMobile app, and the separately developed AnkiDroid client. It does not compare Repeto with AnkiApp, Noji, or other similarly named products.

Repeto vs Anki at a glance

Decision	Anki	Repeto
Availability	Mature public product	Repeto 2.2 is in pre-release; the public iOS listing still ships as Lexiflow 2.1.1
Best fit	Learners who want control, local collection files, and a large add-on and shared-deck ecosystem	Learners who want a more guided creation workflow after launch
Card creation	Manual notes, reusable card templates, text import, media, and add-ons	Current codebase includes manual cards and editable AI-generated proposals; public availability is not yet confirmed
Review scheduler	Legacy scheduler or optional FSRS with extensive controls	Current codebase uses FSRS; parity with every optimized Anki setup has not been demonstrated
Import and export	Delimited-text import and export; `.apkg` deck import and export with optional media and scheduling; `.colpkg` whole-collection import and export, with scheduling included on export and optional media	Current codebase imports supported `.apkg` files and exports decks as `.apkg`; broad round-trip fidelity still needs corpus testing
Platforms	Windows, macOS, Linux, web sync, iPhone/iPad, and Android through AnkiDroid	Web/API/Android are unreleased; the Repeto iPhone/iPad update is in preparation
Offline study	Desktop collections are stored locally; AnkiMobile stores images and audio on-device for offline study	Full offline behavior has not been verified for the pre-release product
Shared content	Public AnkiWeb decks and private package sharing	Current codebase includes a shared-deck market, but its public catalog and scale are not established
Customization	HTML/CSS templates, note types, deck options, and desktop add-ons	Simpler intended workflow, but a much smaller extension surface
Price	Desktop, AnkiWeb sync, and AnkiDroid are free; AnkiMobile is $24.99 in the US App Store	No public Repeto 2.2 checkout should be treated as final before release

Where Anki is better

Anki is available, mature, and extensively customizable

Anki is the practical choice when you need to study now. Its desktop application is open source and supports Windows, macOS, and Linux. The wider ecosystem includes AnkiWeb, the official AnkiMobile app for iPhone and iPad, and the separately developed AnkiDroid app for Android.

That maturity matters beyond platform count. Anki supports reusable note types, multiple card templates from one note, HTML and CSS styling, images, audio, video, scientific markup, detailed deck options, powerful search, and desktop add-ons. Its official product page says it can handle decks with more than 100,000 cards. Repeto has not yet earned comparable evidence of scale or long-term reliability.

Anki gives experienced users more scheduler control

Anki supports FSRS as an alternative to its legacy scheduler. Learners can set desired retention, optimize FSRS parameters from review history, manage learning and relearning steps, and configure deck presets. Those controls are useful when a learner understands how they affect workload.

Repeto’s current codebase also uses FSRS, but shared use of the algorithm does not make the products equivalent. Repeto has not published a head-to-head test against optimized Anki collections, and it should not claim superior scheduling from the presence of FSRS alone.

Anki has the stronger portability record

Anki can import delimited text and packaged decks. Its export tools cover text, individual .apkg decks, and full .colpkg collections. Depending on the export, a package can contain media, note types, templates, scheduling information, and review history.

Repeto’s code includes supported .apkg import and deck export, which is a meaningful design commitment. It is not yet evidence that every custom template, add-on-generated card, modern package variant, media reference, and scheduling history will round-trip unchanged.

Where Repeto is designed to be better

Repeto includes in-product editable AI drafting in its current codebase

Anki is excellent at storing and scheduling cards. Its first-party documentation describes manual note entry, text and package import, shared decks, and desktop add-ons; we could not verify a built-in AI-drafting workflow. Repeto’s pre-release code takes a more guided approach: AI generation produces editable proposals inside a deck, and proposals are reviewed before they are saved.

That distinction is useful for a student whose bottleneck is authoring rather than reviewing. It is an intended Repeto advantage, not a claim that the public product already accepts every document, recording, webpage, or video reliably. Individual source paths need live verification before they are advertised categorically.

Repeto aims to keep Anki migration inside the main product

The current Repeto interface includes a dedicated .apkg import flow rather than requiring a conversion script or third-party bridge. Its codebase also includes .apkg export, so the intended direction is portability both into and out of Repeto.

This is more reassuring than a proprietary text-only export, but Anki remains the reference implementation for the format. Repeto needs a published test corpus before describing the process as lossless.

Repeto includes a conversational card connection in its current codebase

Repeto’s repository includes an OAuth-based MCP connection for supported AI clients, with card and deck tools. The intended workflow is to create or revise study material without manually copying every answer out of a conversation.

This feature is not a public-availability advantage yet. Client-specific setup, authorization, and end-to-end behavior must be checked against the released service before the comparison can say it is available to everyone.

Where Repeto is worse or less proven

Repeto is the smaller and less proven product. Its 2.2 update is still in preparation, while the web, API, and Android surfaces are unreleased under the project’s release ledger. There is no established Repeto add-on ecosystem, no public evidence that it handles 100,000-card collections, and no shared library comparable in maturity to AnkiWeb.

Repeto also has less room for low-level customization. A learner who relies on custom JavaScript, intricate HTML/CSS templates, specialized browser searches, or a particular Anki add-on should assume that workflow will remain better in Anki unless a hands-on Repeto test proves otherwise.

Card creation: control or guided drafting

Anki starts with a note. You define its fields, choose a note type, and use templates to generate one or more cards. For bulk creation, you can import comma-, semicolon-, or tab-separated text. This is predictable and powerful when the source is already structured.

Repeto is intended to start either with a manually written card or an editable generated proposal. The tradeoff is straightforward: generation may shorten the first draft, but it introduces a fact-checking step. A generated card should be compared with its source, split if it asks for several facts, and deleted if it does not deserve future reviews.

Choose Anki’s approach if precise schema control matters more than authoring speed. Test Repeto after release if the blank-card editor is what prevents you from maintaining a deck.

Reviewing: both use FSRS, but the products are not identical

FSRS uses review history to fit scheduling parameters and schedules toward a desired-retention target. In Anki, FSRS sits inside a mature system of deck presets, optimization, filtered decks, burying, limits, and add-on interactions. Anki’s FSRS documentation explains both the benefits and compatibility requirements.

Repeto’s current codebase implements FSRS review flows and records review history. Until a released build is tested against the same cards and response sequence, the defensible claim is that both use FSRS—not that they will produce identical intervals or workloads. For a plain-language explanation, see how FSRS spaced repetition works.

Portability, platforms, and price

Anki wins the current platform comparison. The desktop app stores collection data and media locally, AnkiWeb sync is free, and AnkiMobile stores images and audio on-device for offline study. AnkiMobile currently costs $24.99 as a one-time US App Store purchase; prices can vary by storefront. The desktop version, AnkiWeb synchronization, and AnkiDroid are free.

Repeto cannot make the same availability promise yet. Its iPhone/iPad update is in preparation, and its web and Android products are not recorded as released. There is also no final public Repeto 2.2 price that should be used for a purchase decision today.

A repeatable Repeto vs Anki trial

Run this test when a Repeto beta or release is available. Record the app versions, operating system, and every import option so another person can repeat it.

In Anki, create 20 Basic notes, five Cloze notes, one custom three-field note type, two images, and two audio clips.
Review ten cards once so the package contains a small amount of scheduling history.
Export the deck as .apkg with media and scheduling information enabled.
Import the same package into a clean Anki profile and into Repeto.
Compare note, card, template, tag, media, and review-history counts. Open every custom or media card rather than checking counts alone.
Review the same ten cards with the same Again/Hard/Good/Easy sequence.
Export the Repeto deck as .apkg, import it into another clean Anki profile, and repeat the comparison.
Record every difference instead of reducing the result to a single winner.

The same trial also reveals workflow cost: time how long it takes to create ten additional cards manually in Anki and as reviewed proposals in Repeto. Fact-checking time belongs in Repeto’s total.

Which should you choose?

Choose Anki if you need a dependable product now, advanced customization, desktop add-ons, local desktop study, offline AnkiMobile study, very large collections, or the most established Anki-package workflow.

Consider Repeto after release if you want editable AI drafting and supported .apkg import and export in a product that also uses FSRS. Keep Anki until Repeto passes the package and workflow tests that matter to your own collection.

Official sources

Facts were checked on August 21, 2026.

Repeto vs Anki: which flashcard workflow fits you?