Briefkasten

Last reviewed Sep 13, 2026 · 754 words

Briefkasten is the bookmark manager to pick when you want your saved links to look like a magazine rather than a spreadsheet, and to skip when you want the smallest thing that works. Every card gets an automatic screenshot of the page, tags and categories sit in a sidebar, and sign-in is OAuth rather than a local password. That polish costs a Postgres database, an OAuth provider you have to register, and more moving parts than linkding, which does the same core job on SQLite in about 50 MB of RAM. For a personal link pile, linkding is the safer default; Briefkasten earns its place when the visual dashboard is the point.

What "dashboard" means here

The catalogue files it under dashboards and that is fair: the home view is a grid of screenshot cards you scan by eye, closer to Raindrop.io than to a list of titles. Tags and categories are separate axes (a bookmark has one category and any number of tags), there is a search box across titles and descriptions, and the browser extension saves the current tab with a click. Multi-user works in the sense that anyone whose OAuth identity you allow gets their own bookmarks; there is no shared or team collection. If you are choosing purely on organisation depth, Linkwarden does collections, full-page archives, and sharing on top of screenshots, and has the larger community.

The screenshot pipeline is the first thing to test

Screenshots are what you are paying for, so verify them before you migrate anything. They are captured after save, not at save time, and they depend on a headless browser being reachable; on a small VPS this is the component that quietly fails. Import 5 bookmarks, wait a minute, and check that cards fill in. If they stay blank, fix that before importing 5,000. Screenshots also mean storage: budget roughly 100 to 300 KB per bookmark, so a 10,000-link import costs a couple of gigabytes, which is fine on a disk and unpleasant on a tiny volume.

OAuth-only sign-in is a feature and a chore

There is no local username and password. You register an OAuth application with GitHub, Google, or another supported provider, put the client ID and secret in the environment, and log in through them. For a public instance this is good: no password database to defend, no signup page to abuse. For a LAN-only homelab it is friction, because the provider needs a callback URL it can reach, so you end up with a real domain and TLS even for a box in a cupboard. If you already run Authentik or another OIDC provider, point Briefkasten at it and most of the friction disappears.

The Docker setup is two services and three secrets

Briefkasten needs Postgres. The compose file is the app container plus a database container, and three environment values do the work: the database connection URL, a random secret for signing sessions, and the client ID and secret of your OAuth provider. Schema migrations run on first boot. The 256 MB RAM floor is honest for the app; add another 100 MB or so for Postgres. Backups are a pg_dump plus the screenshot directory, and the export gives you a JSON file you can carry to another tool, which is the property I care about most in a bookmark app.

Check the pulse before you commit

At 1,177 stars and first released in 2022, this is a small project with a single primary maintainer, and commit activity has been quiet for long stretches. That is not fatal for a bookmark app (the feature set is complete and the data exports cleanly), but it changes how you run it: pin the image tag, keep the Postgres dump nightly, and do not assume a security fix arrives the week a Node dependency gets a CVE. Compare that with linkding, which ships regular releases and is the bookmarks category default for a reason.

What I'd do

Run linkding for a personal archive. Run Briefkasten if I wanted a visual link wall I would actually browse, already had an OIDC provider, and did not mind a Postgres container for a hobby app. In that case: register the OAuth app, confirm the screenshot worker fills cards before importing, pin the image tag, and export to JSON every quarter so the day the project goes quiet for good is a Tuesday, not a crisis.