Web Clipper: Settings, History and Language

The settings page

The clipper has a full-tab settings page — not a cramped popup. Everything is configured there: the connection, templates, properties, the interpreter, the highlighter, and shortcuts.

Import and export

Import and export all extension settings, including templates and properties — see 05 Templates and 07 Properties.

This is more important than it sounds. Extension configuration lives locally in each browser. It does not sync through your MDflow account. So:

• Setting up a second machine means importing your settings, not rebuilding them.
• Clearing browser data wipes your configuration.
• Switching browsers starts from scratch.

If you have invested in templates, export them. The export is a file you control, and it is the only backup that exists.

Clip history

The clipper keeps a history of recently clipped pages — useful for checking whether you already saved something, or finding where a clip went.

Usage statistics

View usage over time, by day, week or month. A quiet indicator of whether the tool is actually part of your workflow, or something you installed once.

Language

Choose the interface display language from many supported locales.

This is the extension's own interface. It does not affect your clips — those are in whatever language the page was.

Early access

An optional early-access toggle enables experimental features. Off by default. Turn it on if you want new things sooner and can tolerate rough edges.

What lives where

A summary worth internalizing, since it explains most surprises:

Lives in your browser	Lives in your MDflow account
Your Personal Access Token (02 Connecting to MDflow)	The clipped documents themselves
Templates and their triggers	Their folders
Property definitions	Nothing else
Highlights
Interpreter provider and API key
Clip history and usage stats
Language and shortcuts

Almost everything the clipper knows is local. MDflow receives the finished documents and nothing else — not your templates, not your highlights, not your API key.

That is a good privacy property and an operational hazard at the same time. Export your settings and your highlights periodically — see 04 The Highlighter. They are not backed up by your MDflow account, and nothing will remind you.