Repeto vs Deckbase: AI Flashcards and FSRS

Choose Deckbase if you need an AI flashcard app you can use publicly today on the web, iPhone, iPad, or Android. Consider Repeto if you are willing to evaluate a pre-release product whose current codebase emphasizes FSRS review, editable AI drafts, Anki .apkg portability, and a shared-deck market—but do not choose it on the assumption that those surfaces are already generally released.

Disclosure: Repeto publishes this comparison and therefore has a commercial interest. We link to first-party product sources, state where Deckbase is stronger, and separate Repeto features found in the current pre-release codebase from public availability. Facts and prices were checked on August 21, 2026.

Repeto vs Deckbase at a glance

Decision	Deckbase	Repeto
Public status	Public web, iOS, and Android product	Web app is in pre-release; an iPhone/iPad update is in preparation; Android is unreleased
Best fit	Someone who wants AI creation, FSRS, Anki migration, and mobile review now	Someone evaluating a focused source-to-review workflow before public release
Card creation	Manual cards; AI from chat, PDFs, notes, images, DOCX, and spreadsheets	Current codebase supports manual cards, editable AI generation, and material-ingestion flows; source coverage still needs live verification
Scheduler	FSRS is the default and only scheduler; Deckbase documents adjustable retention targets and automatic background parameter optimization, but not the FSRS version or exact weights	FSRS in the current codebase, with four answer ratings and repository parity tests
Anki portability	`.apkg` import and export are documented, along with CSV and Excel paths, but Deckbase’s first-party pages conflict on which plans include Anki import/export; verify actual account access before migrating	Current codebase imports supported `.apkg` packages and exports decks as `.apkg`; broad losslessness is not yet a public claim
Offline study	Mobile reviews work offline and sync after reconnection	Do not assume full offline use; the unreleased web shell is installable, but every offline action has not been verified
Platforms	Web, iOS, Android	No generally released Repeto app surface yet
Shared content	Deckbase documents a Community where users can publish decks and templates and others can browse, rate, and import editable personal copies; public inventory, searchability, and activity were not verified	Current pre-release codebase includes a free shared-deck market; its live size and availability are not established
API / MCP	Deckbase documents direct REST endpoints and a hosted MCP server; its MCP setup page says tool calls require Basic, Pro, or VIP, although the pricing table also lists MCP under Free	Current codebase includes an OAuth-based MCP connection; client-specific public availability still needs verification
Listed price	Free; Basic $5.99/month or $59/year; Pro $11.99/month or $119/year	Public Repeto pricing and availability should be rechecked at release

The most important difference is not a checkbox. Deckbase can be tested as a released product now. Repeto is still evidence from a codebase and release plan until its owner records a public launch.

Where Deckbase is better than Repeto today

Deckbase is available on more real devices

Deckbase offers web, iOS, and Android access. Its official download page says mobile reviews run offline and that review history syncs after reconnection. A student can therefore test the complete create-review-sync loop on the devices they already use.

Repeto cannot currently make the same availability claim. Its web app is marked pre-release, its iPhone/iPad version is an update in preparation, and Android is unreleased. Even if a development deployment is reachable, that is not the same as an intentional public release.

Deckbase already ships the closest version of Repeto’s proposed bundle

Deckbase combines AI drafting, editing, FSRS, media, Anki import/export, cloud backup, direct API access, and a hosted MCP server. That makes it the closest direct alternative in this comparison set. You do not need an add-on to turn a PDF or prompt into cards, and you can export a generated deck back to Anki as .apkg.

Deckbase also documents offline mobile review. Repeto’s current codebase has offline-capable pieces, but it has not published a verified matrix covering offline opening, reviewing, editing, generating, importing, and later sync.

Deckbase publishes prices and quotas

Deckbase lists a free plan and two paid plans. Basic includes 250 AI generations per month; Pro includes 600. The page also states storage and new-card limits, although its descriptions of Free-plan AI, MCP, and Anki access conflict with feature-specific pages. Repeto’s price-to-limit comparison cannot be completed responsibly until the pre-release product has a public offer that can be checked.

Where Repeto’s pre-release direction may differ

These are target differences to test, not demonstrated advantages.

Repeto intends a versioned review contract

Repeto’s current repository uses a four-button FSRS review flow—Again, Hard, Good, and Easy—with scheduling fixtures intended to keep clients consistent. Deckbase’s documentation says FSRS is its default and only scheduler, starts with default parameters, automatically adapts from review history, and lets users adjust the retention target. It does not identify the FSRS version or publish the exact default or learned parameter weights.

The missing public detail is a question for a hands-on test, not proof that Deckbase lacks a rigorous implementation. Repeto’s intended contract may help someone who wants reproducible scheduling behavior, but it does not prove better retention and still needs public, versioned testing.

Both products describe shared-deck workflows

Deckbase’s homepage says users can publish decks and templates to its Community, where other users can browse, rate, and import an editable personal copy. We did not verify an unauthenticated public catalog, search quality, inventory size, moderation, or activity.

The current Repeto codebase includes browse, publish, install, rating, reporting, and .apkg download routes for a free shared-deck market. Its portability and moderation design may differ, but it remains pre-release and has no demonstrated live inventory or network effect.

The products document different source scopes

Repeto’s product plan includes pasted text, files, web links, audio/video, external AI context, and grounded research that carries source URLs into draft cards. Deckbase officially documents chat, PDFs, pasted notes or text, images and OCR, DOCX, spreadsheets, Anki inputs, and article-oriented workflows. We did not find first-party documentation for uploaded audio/video or live source-grounded research.

Deckbase’s documentation gap does not establish that those inputs are absent. The honest comparison is a test plan: test Deckbase now, then run the same audio, video, webpage, and research request in Repeto only after those paths work in its release environment. Repeto should not claim broader support until its own paths and the corresponding Deckbase paths have been checked directly.

Where Repeto is worse or less proven

Repeto is the higher-risk choice today.

It has no generally released Repeto app surface to evaluate over a full week.
Android is not available, while Deckbase ships Android.
Its offline behavior has not been published as a tested capability matrix.
Supported .apkg import and export exist in the codebase, but broad fidelity across custom templates, media, scheduling history, and modern package variants still needs a recorded corpus result.
Its shared market has no demonstrated public inventory or network effect.
There is less public evidence about support response, reliability under exam load, and long-running sync behavior.

Deckbase’s first-party pages are internally inconsistent. Homepage metadata still mentions a 500-card Free limit and Premium starting at $4.99 per month, while the homepage hero and current pricing table say unlimited decks and cards and list Basic at $5.99 per month. The pricing table places AI card generation and MCP integration under Free, while feature-specific AI and MCP pages say paid access is required. Its pricing page places Anki import/export on Basic and Pro, while the Anki import hub says import is free on all plans and the Anki generator says .apkg export is free. Verify live in-account entitlements immediately before purchase or migration.

Card creation: similar promise, different verified scope

Deckbase has the simpler current answer: upload a supported file or start a chat, let AI draft cards, edit the results, and add them to review. It supports PDFs, DOCX, notes, images and OCR, Excel/CSV, and Anki imports. AI images and text-to-speech audio can enrich cards.

Repeto’s pre-release workflow also keeps generated cards editable before study. Its intended differentiator is not merely “AI makes cards”; it is one review surface for material from several source classes, including research and AI conversations. Until live paths are verified, test only the source you actually need rather than buying the promise of “anything.”

Reviewing: both say FSRS, but inspect the controls

FSRS is a family of scheduler versions and configurations, not a complete description of an app’s behavior. During a trial, check:

whether you rate recall with two or four choices;
whether the next interval is visible before rating;
whether you can change target retention or learning steps;
how imported cards are scheduled on day one;
whether undo restores the previous state;
what happens to reviews completed offline.

Repeto’s current codebase is designed around four ratings and explicit review history. Deckbase is the only product here that can currently be tested on public mobile apps, so observed behavior should outweigh a specification.

Anki import and export: test history, not only card text

Deckbase documents .apkg import and export. Its FSRS documentation says cards, notes, and media transfer on import, but review history and scheduling data do not; imported cards start fresh with FSRS intervals. Successful content transfer is therefore not preservation of learning state.

Repeto imports supported .apkg packages and exports decks as .apkg in its current codebase. Repeto should not call the path universally lossless until a current test corpus covers basic, cloze, media, custom templates, non-Latin text, review history, and modern package variants.

If you already have a valuable Anki collection, keep the original backup and migrate one active deck first.

Run the same 30-minute trial in both apps

Deckbase can be tested now. Run the Repeto side only when you have legitimate access to a pre-release build; do not treat a landing-page demo as a substitute.

Pick a two-page source you understand well. Include one heading, one image, one table, and at least one fact that is easy to misread.
Ask each app for 15 cards from that source.
Count focused cards, unsupported answers, duplicate prompts, and cards you would delete.
Time how long it takes to approve and edit the batch.
Add five manual cards, including one image and one cloze-style prompt if supported.
Complete a review session and record the intervals offered for the same answer pattern.
Export the deck to .apkg, import it into a fresh Anki profile, and inspect text, media, card count, templates, and scheduling state.
On mobile, go offline, complete ten reviews, reconnect, and verify that progress appears on another device.

Use the same source and scoring sheet. A faster generation animation is irrelevant if the batch needs more repair or the exported deck loses information you rely on.

Which should you choose?

Choose Deckbase if you need a released web/iOS/Android product now, want AI drafting from common document formats, need offline mobile review, or want an existing FSRS-and-Anki workflow at a published price.

Consider Repeto if you are comfortable joining a pre-release evaluation and care about its target combination of explicit four-rating FSRS, source handling that still needs live comparison, its own shared-deck and portability design, and Anki portability. Re-evaluate this recommendation after Repeto records a public release and publishes import, offline, and sync test results.

There is no evidence-based reason to leave a stable Deckbase workflow for an unreleased promise. Test Repeto later only if its verified source handling, portability, or review-contract details solve a concrete problem for you; Deckbase already documents a Community sharing workflow.

Official sources

Checked August 21, 2026. Deckbase facts come from its first-party pages; Repeto availability follows the project’s release ledger rather than the presence of development code.

Repeto vs Deckbase: which AI flashcard app fits your workflow?