Exporting your flashcards: CSV, JSON and Markdown without losing the context
Your cards should outlive any single app. What actually travels in each Kardo export format, how to bring a deck into a spreadsheet or another tool, and the traps that quietly strip context.
Reviewed by Kirill Oleinichenko ·
Published Updated 5 min read
On this page
A flashcard deck is a small asset with a long life. The app you made it in will not be the app you use in five years, and the lessons the cards came from are already behind you. So it is worth asking a plain question about any study tool you invest months into: what exactly do I get to take with me?
This is a practical walkthrough of the export formats Kardo offers — the TSV file the app labels "CSV (Anki)", JSON, and Markdown — and of the quiet differences between them. What matters in each is which parts of the card it preserves.

What a card actually contains
Most flashcard tools pretend a card is a front and a back. Under that model every export is trivial and every export loses the same things.
A card from a real lesson is richer. Take a single Spanish word your teacher used last Tuesday. The useful record holds more than despertarse = to wake up:
- front —
despertarse - back — to wake up
- context —
Me despierto a las siete todos los días.— the sentence it was actually said in - type — verb
- difficulty — A2, roughly where the lesson was pitched
Those are the exporter's own field names. The context line carries the memory, and it is the first field most exports drop, without a warning. When you review the word alone, you are memorizing a pairing. When you review it inside its sentence, you are rehearsing the word the way you will actually need it: in a stream of speech. An export that keeps the front and loses the context leaves you a poorer deck than the one you had.
The file labeled "CSV (Anki)" is really a TSV
Start with the format most people reach for first. Kardo's export button says "CSV (Anki)", and the file it downloads is a tab-separated text file with a .tsv extension and a UTF-8 byte-order mark. The tab separator is what makes the file open cleanly.
What it contains is one card per row, with the five fields above as columns. A trimmed example — two rows of a lesson about mornings — looks like this (the gaps between columns are single tab characters, which is what a .tsv reader expects):
front back context type difficulty
despertarse to wake up Me despierto a las siete todos los días. verb A2
la alarma alarm La alarma no sonó y llegué tarde. noun A2
Three of the fields are worth defending. context is the sentence from your lesson; type and difficulty let you sort a mixed deck later — pull out the verbs, or hide everything above your current band. The other defensible choice is the delimiter itself: Spanish sentences contain no tab characters, so column boundaries never need escaping, and spreadsheets split the columns identically on every machine — no more "it opened as one column" after a spreadsheet guessed a semicolon because the locale said so.
The traps, in the order they bite. First, line breaks: a multi-line context sentence is flattened to a single line on export, because a raw line break would split one card across two rows. That loss is deliberate: it keeps a long quote readable on one line and every card on its own row. Second, encoding: the leading byte-order mark is what keeps despertarse and señor intact when the file is opened in spreadsheet apps that would otherwise guess a legacy code page and show ? — if you re-save or re-convert the file, keep UTF-8. Third, and most dangerous: a two-column importer will happily put the context text on the back of the card. Every row imports without an error, and the cards are useless for review. Check where the sentence landed before you trust the import.

JSON — for keeping everything, forever
JSON keeps the structure of each card. A single card round-tripped through a Kardo export looks like this:
[
{
"front": "despertarse",
"back": "to wake up",
"context": "Me despierto a las siete todos los días.",
"type": "verb",
"difficulty": "A2"
}
]
Optional fields are omitted when a card has none — front and back are always present, context, type and difficulty appear when there is something to say. Exporting everything at once wraps the same card objects in an envelope — exportedAt, totalCards, and a lessons array of { title, date, cards } — while a single lesson exports the flat array shown above. This is the format to choose when the destination is a program: a script that rebuilds the deck somewhere else, a statistics notebook, an archive you open again in three years. The rules are simple because the structure is explicit — no delimiter to escape, no column-position guessing.

One honest caveat: JSON holds your cards. The review history and the spaced-repetition schedule stay in the app that produced it. Moving decks between tools resets the schedule — unavoidable, and worth knowing before you migrate a deck you have been reviewing for months.
Markdown — for humans, notes and the archive
Markdown is the format for reading. It is what you would send to a study partner, paste into your notes app, or keep in the same folder as the lesson summaries. The export is a titled table, one row per card:
# Morning routine
| Front | Back | Context | Type | Difficulty |
| ----------- | ---------- | ---------------------------------------- | ---- | ---------- |
| despertarse | to wake up | Me despierto a las siete todos los días. | verb | A2 |
It survives text editors, note apps, and version control, and it reads well as plain text: you can read a Markdown export on a phone in a queue and actually learn from it. (A plain-text .txt variant exists too, for the same reason, with one card per line.)
Kardo has no direct export to Mochi Cards. Mochi imports Markdown files, so the Markdown export is the way there. In every case the export should be a complete copy of the deck, with every field.
The question that decides the format
If you take one habit from this article, make it this decision rule:
- Spreadsheet or Anki import → the TSV labeled "CSV (Anki)". Keep it UTF-8; check that the context landed in the right column.
- A program or a long archive → JSON.
- People, notes, reading → Markdown.
Whichever you choose, export before you need it. A backup you make on the day you are leaving a tool is a backup made under pressure, at the moment you have the least patience to check the output. Ten seconds of choosing the right format in a calm week saves an afternoon of repairing a stripped deck later.
Your words came from a real conversation with a real teacher. The export is how they stay yours.
Kardo Editorial
Every lesson, already exportable
The words the bot extracts are yours to keep — the same fields this article walked through, ready for a spreadsheet, an archive, or another app.
Start free