Your lesson notes, after the lesson.

Preply closes a lesson’s Canvas the moment it ends, and everything your tutor wrote goes with it. This extension keeps a copy — offline, with every version.

Add to Chrome Add to Firefox Add to MS Edge

The archive reader: classrooms on the left, that classroom's pages in the middle, the archived document on the right.

One classroom per tutor. Each page listed once, with every version behind it.

One button, and you stop losing notes.

A single archive button joins the Canvas toolbar during a lesson. Click it and the page is stored. Forget, and it saves on its own a minute after the last edit.

The Preply Canvas toolbar with one extra archive button at its right end, marked by a red arrow.

The whole footprint inside Preply, styled from the buttons already there.

Nothing leaves your browser.

No server, no account, no analytics — there is nothing to send anything to. Everything lands in local storage on your own machine, and uninstalling deletes it all.

The only traffic it causes goes to preply.com itself, while you are already on a lesson page, to copy the images from your Canvas.

The parts that were actually hard.

Versions stay whole

Every save is stored complete and independent, never as a chain of differences. A damaged file costs one version, not the history behind it.

Search that knows Polish

Accents and case folded across a classroom — and ł is a letter no normalisation decomposes. Type slonce, find słońce.

Lines break where they broke

The reader reproduces the width, size and typeface of Preply’s editor, so an archived page wraps exactly as it did in class.

Images that survive

Preply serves them from links that expire in hours. They are copied in at capture, or the archive would quietly rot.

Running it from source.

The three store listings are the way in. This is the other one — for reading the code, changing it, or running what is on master before a store has it. Review takes days; a branch takes none.

Firefox: about:debugging → This Firefox → Load Temporary Add-on → pick src/manifest.json. It goes when Firefox restarts: a permanent install has to be signed.
Chrome and Edge: run bash tools/package.sh, then chrome://extensions (or edge://extensions) → Developer mode → Load unpacked → pick dist/chrome/

No build step, no bundler, no minifier: src/ is what ships. What you read is what runs.

Only pages you open while it is installed can be captured. Lessons already past are out of reach.

Thanks.

To Paula, my Polish tutor and a formidable authority on sękacz, and to Shuang laoshi, my Chinese tutor. This exists to keep what the two of them teach me.