A bookmarklet is a bookmark that runs a small piece of code on the page you are looking at, instead of taking you somewhere else. You keep it on the bookmarks bar and click it, and it acts on what is in front of you — saving the page to your library, sending it to a reading queue, stripping the clutter out of an article, copying the title and link in a tidy format. You install it by dragging a button onto the bar, and it is gone the moment you delete it.
That last part is why bookmarklets have outlived every prediction of their death. A bookmarklet does nothing until the moment you click it, and then it only touches the page you clicked it on. An extension is granted standing access and keeps it. For the narrow job of "save this page to the place I keep things", that difference is worth understanding before you install anything.
How a bookmarklet actually works
An ordinary bookmark holds a web address, and clicking it takes you there. A bookmarklet holds instructions instead — a javascript: URL — and clicking it runs those instructions against whatever page is currently open.
Everything follows from that:
- It runs only when clicked. No background process, no timer, nothing watching your browsing.
- It runs in the page's own context, which is what lets it read the title, the URL, the selected text or the article body.
- It is stored like any other bookmark, so it lives in your bookmark tree and travels with it.
- It is frozen. The code is whatever you saved and cannot change itself. To update it, you replace it deliberately.
Installing one is usually a drag: a page offers a button labelled something like Save to… and you drag it onto your bookmarks bar. You can also create a bookmark by hand and paste the code into its address field. What you cannot generally do is paste that code into the browser's address bar — browsers block it there on purpose, because that paste has been a scam technique for years. If instructions tell you to do it, close the page.
What a bookmarklet is not
- Not a browser extension. An extension is installed software with declared permissions, a background life and the ability to update itself. A bookmarklet is a bookmark.
- Not a keyboard shortcut. Shortcuts trigger things the browser already does; a bookmarklet adds behaviour it does not have.
- Not an installed web app. Those open a site in its own window; a bookmarklet stays on the page you are on.
- Not a saved page. Clicking one may cause a page to be saved, but it stores nothing itself — it is the button, not the filing cabinet.
What people actually use them for
In practice most useful bookmarklets do one of four things.
- Save the current page to a library. The classic case: your bookmark manager or read-later service offers a one-click button that files the page without you leaving it.
- Send a page somewhere else — a notes app, a task list, an archive, a reading queue.
- Clean up a page for reading or printing. Strip the furniture, widen the text, remove what is not the article.
- Copy a link in a usable shape. Title and URL together, formatted how you want them, rather than a bare address you then have to label.
Notice the pattern: all one-step actions on a page you are already on. Anything needing memory between clicks, a background process, or its own interface has outgrown the form.
Bookmarklet or browser extension: what each one costs you
Both do the save-a-page job. They cost you different things, and the honest comparison is not about capability.
The bookmarklet's advantage is scope. It has no standing permission to read your browsing and no ability to act when you are not looking. It is also portable in a way extensions are not: being a bookmark, it syncs wherever your bookmarks sync, including browsers with no extension store worth speaking of.
The trade-off it hides: it is stuck at one click on one page. It cannot add a right-click menu, answer a keyboard shortcut, show what you have already saved, or work at all on pages where it is blocked. It also cannot fix itself — if the service it talks to changes, the button quietly stops working and you may not notice for weeks.
The extension's advantage is presence. A keyboard shortcut, a toolbar indicator, a right-click menu, offline queuing, a view of your existing library. For anyone saving many pages a day, that is a genuinely faster workflow.
The trade-off it hides: you are granting persistent access, usually to every site you visit, to software that updates itself. Extensions change hands, and one that was trustworthy when installed is not automatically trustworthy a year later. Not a reason to avoid them — a reason to keep few and know what each is for.
The rule: if you save a handful of pages a day and want the lightest footprint, a bookmarklet is enough; if you save constantly, an extension earns its permissions. Where either would do, the deciding question is the one that decides most of these choices — where you go looking afterwards, the subject of where your saved links should live.
And worth saying plainly: your browser already saves a page with a built-in shortcut. Either tool earns its place by doing something the browser cannot — not as a more elaborate way to do something it already does well.
Why a bookmarklet sometimes does nothing when you click it
Silence is the usual failure mode, which makes it confusing. Run through these in order.
- The page has not finished loading. The bookmarklet acted on a document that was not ready. Wait and click again.
- You are on a browser page rather than a web page. Settings, the new tab page and error pages do not run page code. Nothing will happen, and nothing is wrong.
- The site's security policy blocked it. Sites can restrict what code runs on them, which particularly affects bookmarklets that fetch further code from elsewhere. Browser behaviour here varies, so the same button can work on one site and not the next.
- The site changed underneath it. Bookmarklets that read a page's structure depend on it staying put, so a redesign breaks them — the most common cause of one that used to work.
- The saved code got mangled. Some bookmark editors, importers and cleanup tools trim or reject
javascript:addresses. If yours stopped working right after a migration, this is why. - The service behind it needs you signed in. Save buttons post to an account; if your session expired, the click goes nowhere visible.
Can you use a bookmarklet on a phone?
Yes, with a caveat: phone browsers have no bookmarks bar, so there is no button to click. The workaround depends on the browser — some let you type a bookmark's name in the address bar and pick it from the suggestions, which runs it on the current page; others expect you to open it from your bookmarks list. Both are clumsier than a tap.
On a phone the share sheet usually wins: the operating system already has a proper mechanism for sending the current page to another app, and most save services offer one. Use the bookmarklet on the desktop and the share sheet on the phone, and let both feed the same library — building a save-for-later system covers making that loop hold together.
How to judge whether a bookmarklet is safe to keep
A bookmarklet runs with the same access as the page you are on, including pages where you are signed in. That is not alarming in itself — it is exactly what lets a save button read the article you want to save — but it does mean the source matters.
- Prefer the button from the service you already use. It is maintained by the people whose product it is.
- Be wary of anything that loads more code from elsewhere. A bookmarklet that fetches a script at click time is not frozen: whatever sits at that address today can be replaced tomorrow without your involvement.
- You can read it. Open the bookmark's properties and look. You need not understand every character to notice an address that has nothing to do with the service you thought you were using.
- Never paste code into the address bar because a page told you to, and be equally suspicious of a bookmarklet offered as a way to unlock or bypass something in an account you are signed into.
- Keep the collection small and clearly named. A bar of mystery buttons installed a year ago is a set of decisions you can no longer audit; if you keep several, a start page that surfaces saved links is a tidier home than a crowded bar.
FAQ
Do bookmarklets still work in modern browsers?
Yes, on the desktop. No browser has removed the mechanism, and they still work on ordinary web pages. What has changed is the edges: browsers block the code being pasted into the address bar, some sites restrict what may run on them, and phone browsers make them awkward to trigger.
Are bookmarklets safe?
The mechanism is safe; the specific code varies. A bookmarklet only runs when clicked, but while it runs it can see the page you are on, including one you are signed into. Install them from the service they belong to, prefer self-contained code, and treat any bookmarklet promising to unlock or bypass something as hostile.
Why does my bookmarklet work on some sites and not others?
Usually the site's own security policy, or the site changing its structure — bookmarklets that read a page's contents depend on it, so a redesign makes the button fail silently. Browser pages such as settings and new tab never run page code at all.
Why do fewer services offer a bookmarklet now?
Because extension stores and mobile share sheets became the default way to distribute a save button, and because site restrictions made bookmarklets less predictable. Plenty of services still keep one as the fallback for browsers they do not otherwise support, so it is worth checking a product's help pages rather than assuming the option is gone.
Do bookmarklets sync between my devices?
They sync wherever your bookmarks sync, because that is what they are. One exception: some import tools and cleanup utilities strip javascript: addresses, so a bookmarklet can be quietly lost in a migration that moved every other bookmark faithfully.
Next step
If saving pages is something you mean to do and keep not doing, capture friction is a likelier cause than discipline. Install the save button your library already offers, put it where your hand finds it without thinking, and give it a week. If you use it, the button was the missing piece; if you do not, the problem is further down the chain and it is the library that needs attention. More on building one you will actually open at BookmarksMyWeb.
