errorboard comes in three shapes that share one account: the Windows app that watches whatever you study in, the handwriting notebook, and the snap-a-photo studio. This guide walks each one end to end.
The three surfaces aren't separate tools: they're one loop. You make a mistake, errorboard auto-marks it, turns it into an improvement plan, and that plan flows straight back into your notebook and error log so your next session targets exactly what you got wrong. Here is the full loop:
Work as normal, on screen (desktop app), by hand (notebook), or on paper you photograph (studio). The notebook auto-marks each step a moment after you pause; the desktop app marks the window when you hit the hotkey. The detection mode decides how it judges the work.
For every flagged slip the model writes a short plan: what went wrong, the correct approach, and what to drill next. In the studio and notebook this comes back on screen straight after marking; on the desktop it's written into the entry.
The mistake, the screenshot/photo of where you slipped, and the improvement plan all land in your per-topic error log. With Pro these sync across every surface, so a calculus slip on the iPad joins the same log as one from the desktop.
Before your next session, reopen the notebook or the log, re-work the flagged problems, and mark each one resolved once you understand it. Auto-mark confirms the fix, and you stop repeating the same mistake.
The desktop app is the core of errorboard. It lives in your system tray with no window of its own and captures the program you study in on demand, so it can watch a browser question bank, a PDF past paper, OneNote, or anything else on screen.
Run errorboard-setup.exe.
If Windows SmartScreen warns you, click More info then Run anyway:
the app is new and not code-signed yet. The settings window opens the first time it runs.
Open the errorboard Pro tab and enter the email and password from your subscription. The app stays idle until you are signed in.
On the Detection tab, choose Standard, Question bank, or Solve and set a default topic for when the model can't infer one.
Click away and errorboard sits quietly in the tray. Tick Launch at sign-in on the Capture tab if you want it ready every time you boot.
errorboard does not film your screen. It captures a single frame only when you ask it to, by pressing the capture hotkey or the tray button. At that moment it grabs whatever window is in focus, sends that one frame to the cloud vision model, and if a mistake is found it files it in your error log.
Open settings from the tray icon any time. There are five tabs:
Shows what errorboard is doing right now and lets you set a session topic: force every mistake this sitting under one subject (e.g. Calculus). Leave it blank to auto-detect per capture.
Choose your logs folder (defaults to Documents). Optionally point everything
at a single .docx, or leave it blank for one file per topic. Toggle
Launch at sign-in here.
Pick the mode, a default topic, and two sliders: Min. confidence (how sure the model must be before it logs; raise it for fewer, higher-quality flags) and Ignore repeats for (a cool-down so the same slip isn't logged twice in a row).
Rebind the three global hotkeys below to whatever you like.
Your account: email, password and the backend URL. Sign in or switch accounts here.
These work from any app, even with the settings window closed. Defaults:
Write maths by hand on an iPad, a tablet, or any browser at errorboard.com/notebook, or get the Windows app for it from the download page. It marks your working as you write.
Use the pen, highlighter, eraser, shapes and lasso-select tools. Tap + Add page for a fresh sheet, or Import PDF to write directly over a worksheet or past paper.
Type an optional topic so logs file neatly. With auto-mark on (the default), errorboard checks each step a moment after you pause. Prefer manual? Turn it off and tap Mark this page now.
Upload or paste the official solutions / mark scheme. When set, marking uses it as the answer key and awards marks against it instead of solving from scratch.
Mistakes appear in the side panel. Lasso a stroke and hit Delete to clean up, and mark anything resolved once you've understood it. Every notebook keeps its own log.
Already finished on paper? Open the studio on any device, set an optional topic, then Take a photo or choose an image of your working and tap Mark it. errorboard returns an improvement plan and logs each mistake. Make sure your final answer is visible in the photo before you mark it.
The mode tells errorboard how to judge what it sees. Pick it on the Detection tab (desktop) or the mode selector (notebook / studio).
Every mistake lands in a plain Word document, one <topic>_errors.docx per
subject by default, in your logs folder (Documents on the desktop app). Each entry has:
Because they're ordinary .docx files you can open, search, print or annotate them
anywhere. With Pro, logs sync to your account so the same subject grows whether you studied on
the desktop, the iPad notebook or the studio. Review one before your next session and you stop
repeating the same mistake. New to the method itself? Read
how to keep an error log for studying.
Logging mistakes is half the loop; the quiz bot is the half that brings them back. Connect Discord from your account page and the bot turns your logged mistakes into fresh practice questions:
Duels need a friend connection first: swap friend codes on the account page. Friend sharing is opt-in — friends see your subject summary by default and your full log only if you choose, and you can pause sharing entirely. Both the quiz bot and duels are Pro features.
Prefer spaced repetition in Anki? The bot can turn your logged mistakes into a ready-made deck — question on the front, the correct answer, your answer and the why on the back, tagged by topic. It works on the free plan; you only need a linked Discord account. Setup:
On your account page, copy your link code, then run /link code:XXXX in a DM with the errorboard bot. Already linked for quizzes? Skip this.
Type /anki in the
DM. Optional filters: topic: to export one subject,
days: to only take recent mistakes (e.g.
/anki topic:Calculus days:30). The bot replies with an
errorboard-anki.txt file.
Download the file, open Anki, go to File → Import and pick it. The file pre-configures everything — just confirm. Cards land in an errorboard deck (or errorboard::Topic if you filtered), using the Basic note type.
Re-run /anki whenever you've logged new mistakes and import
again: cards with an unchanged question update in place rather than duplicating. On the
Windows desktop app you can also export a native .apkg deck directly, no
Discord needed.
The export also works in reverse: upload any Anki deck and the bot quizzes you on it — multiple-choice with answer buttons, or type-your-answer questions the AI marks for you. Your answers feed the same spaced-repetition schedule as your mistakes, and cards that are due can show up in your daily quiz DM. Setup:
In Anki, select the deck, go to File → Export, choose Anki Deck Package (.apkg) and tick “Support older Anki versions” (the bot can't read the newest format without it). Media isn't imported, so you can untick “include media” to keep the file small — text-only cards work best.
In a DM with the bot, type
/deck import and attach the .apkg file. Add an
optional name: to rename it. Up to 10 decks and 2,000 cards
per import; re-importing a deck with the same name replaces it.
/deck quiz tests you on a random deck, or pick one with deck: and a style with type: (multiple choice / type your answer). /deck list shows what you've imported and /deck delete removes one.
Importing decks is free for any linked account; deck quizzes (like all quizzes) are a Pro feature. Image- and audio-only cards are skipped, and cloze cards become fill-in-the-blank questions automatically.
Still stuck? Email support.