Fin: fast import notes

AnkiWeb addon 690490497

Imports notes from a text format using inherited metadata for decks, note types, and tags, plus line-based fields, bold/italic/link markup, and nested lists.
AI-generated summary; may contain mistakes.

card-creationimportformatting

Open on AnkiWeb Ask about alternatives

AnkiWeb

Rating
0 (πŸ‘ 0 Β· πŸ‘Ž 0)
Updated
2026-09-09
Anki versions
2.1.1~
Description language
en

Maintenance

active

  • Last update or commit was 22 days before the snapshot (2026-09-09).

GitHub

No GitHub repository linked.

Will it work on my Anki?

Version branches
Min AnkiMax AnkiUpdated
2.1.1+2026-09-09
History across monthly snapshots

Loading…

Similar addons

Anki Notes Generator

Generates Basic and Cloze Anki flashcards from .md, .txt, and .markdown notes using Ollama AI, with duplicate detection, auto-tagging, custom prompts, and English/Italian interface.

card-creationaiimportduplicatescloze

Rating 1 πŸ‘ 1 Β· πŸ‘Ž 0 Anki 2.1.66~ Updated 2026-03-06

Description

Fin: Fast import notes Fin is two things: it's a text document format and it's an Anki add-on that lets you import notes in the Fin text format. Exigence Creating notes in the default Anki editor is cool and all, but it can be hard to design your notes/cards when you can only (really) look at one of them. But when you design your notes in a text file, manually inputting them into Anki is a pain and is the kind of friction that can/should be eliminated. So with Fin, hopefully you can design notes in a text file and import them in a fast and efficient manner. There seem to be already add-ons (plus native importing), but I'm not a big fan of their syntax. Syntax of Fin Fin closely models what you would enter into the Anki note editor. There are two kinds of data: metadata and field data. Metadata denotes decks, note types and tags, and flow down . This means that when you enter in some metadata at the top of the file, all notes below them will be given that metadata, unless you redefine them. Here are some examples of metadata: #deck: Default #type: Basic #tags: foo, bar You can only input metadata at the top of the file or between notes (it wouldn't make sense anyways to enter in metadata in the middle of a note). After entering metadata, everything else will be viewed as field data. Field data is line-based, i.e. one field per "line," and you can have markup that will be translated into HTML. A "line" is not actually limited to a single real line; if a line starts with whitespace, it will be considered as part of the previous field. For example: What are some traits of an apple? Apples can be juicy, colorful, and nutritious. Apples can have many different colors, from red to green. Apples can have sweet juice, but also sour juice. But all apples are nutritious (don't quote me on that). Despite covering 5 lines, this note maps to the Default note type, which has two fields. This is because the 3rd to 5th lines start with a space (it can be multiple spaces or even tabs). If you want a line of space within a single field, you can use a line that only has whitespace. For markup, only bold , emphasis , and links are defined as of now. Both the bold and emphasis markup are borrowed from Org-mode, because it's more intuitive than Markdown's markup for them. *This* is bold. /This/ is italicized (emphasized). For links, I was inspired by a markup language whose name I have forgotten, because both Markdown and Org-mode's link syntax is abyssmal. To learn more, click [here]@https://example.com/funny/haha.html. What is inside the square brackets are used as display text, and what is after the @ symbol is used as the URI. I personally find it more intuitive: the square brackets make the display text look like a button, and the @ shows a morphism from the display text to the URI. For links without display text, just have square brackets with nothing inside. Now, the markup described up until now are single-line markup, meaning that they are interpreted on a line-by-line basis, so you can't bold multiple lines (for now). For multi-line markup, you can have unordered and ordered lists. Description lists are coming soon. To mark up an unordered list: This is an unordered list: - Red - Orange -- Orangey-yellow - Yellow -- Lemon - Green -- Forest -- Grass - Blue -- Ocean --- Fish? - Purple - Magenta To mark up an ordered list: This is an ordered list: . 3 .. 1 . 4 .. 1 ... 5 .... 9 . 2 .. 6 . 5 .. 3 .. 5 .. 8 .. 9 You cannot mix them together for now, but I might add it as a feature. You can also embed HTML5 tags, like Markdown, and it should work. All work is done in the git repository stored in https://codeberg.org/10sun/fin .