Clip any web page straight into your Trail knowledge base — one click, on the page you are already reading.
Users
4
0 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#304K
#249K among extensions
Version
0.2.1
updated 28 Aug 2026
Users
monthly, 2 months
Latest, 18 Oct 2026:4 usersMove the mouse over the chart for any month
Ratings count
monthly, 2 months
Latest, 18 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Trail Web Clipper
Trail Web Clipper saves the page you are reading into your Trail knowledge base with one click.
It clips the ARTICLE, not the page. Mozilla's Readability extracts the body text and discards navigation, banners, cookie notices and related-article boxes. What is left is converted to markdown, so headings, lists, links and quotes survive — the structure is what lets Trail build the content into what you already know, instead of receiving a lump of text.
WHAT IT DOES
• Pick which knowledge base the clip lands in, from a list fetched live from your own Trail.
• Add tags if you want to. It does not invent them.
• The status line shows which Trail the clip will go to BEFORE you click, so a clip never quietly goes somewhere you did not intend.
• After clipping, it shows the source address as a receipt.
IT IS IDLE UNTIL YOU CLICK IT
There is no background script running on the pages you visit. The extension asks for "activeTab" and "scripting" — permissions that grant access to the single page you are on, in the single moment you press the button. The extraction code is injected on that click and is gone afterwards.
It cannot follow your browsing. Not because we promise not to, but because we did not ask for permission to.
YOU CHOOSE THE SERVER
By default the extension uploads to app.trailmem.com. The server address is a setting, not a constant: point it at your own Trail — including one running on your own machine — and the clipped page never reaches us at all.
The only things stored on your device are the server address and your API token. The token is sent to exactly one place: the Trail server you configured, as the credential for your own upload.
REQUIREMENTS
You need a Trail account and an API token (Settings → Developer in your Trail).
Setup, server choice and what each error message means:
https://docs.trailmem.com/web-clipper/
Browser-internal pages (chrome://…), the Web Store itself and PDF viewers cannot be clipped. Browsers do not let extensions read them.