getbookmarklets.com

Get Bookmarklets (getbookmarklets.com) is a browsable collection of bookmarklets and userscripts that you install by dragging a link into your browser's bookmarks bar. It is relevant if you want small, single-purpose browser tools without installing an extension, and it also lets you share scripts and submit your own. The site describes itself as "browser scripts you can trust" and organizes content around a simple "How it works" explanation.

What the site offers

• A catalog of bookmarklets and userscripts you can browse and install with a single drag.
• Sharing and submission: you can share scripts and submit your own to the collection.
• Source visibility: at least some entries expose the underlying script source. The Bandcamp Purchases Export entry, for example, lists a source URL pointing to a GitHub Gist and a "Source code" link.

The catalog is community-oriented rather than a single vendor's product line, so the value depends on whether the specific script you need is listed.

How installation works

A bookmarklet is a bookmark whose address is JavaScript instead of a URL. Dragging the install link to your bookmarks bar saves that script as a bookmark; clicking it later runs the script on the page you are viewing. Userscripts are longer scripts typically run through a userscript manager.

The practical steps:

1. Make sure your bookmarks bar is visible in your browser.
2. Open the script's page on Get Bookmarklets.
3. Drag the install link into the bookmarks bar (or create a bookmark manually and paste the script as its address).
4. Navigate to a page where the script applies and click the bookmark to run it.
5. Confirm the expected result — for example, an export file downloads or the page changes in the way the script describes.

Expected result: the script runs only when you click it, and only on the page you have open.

What to check before installing

Because bookmarklets execute code in the context of whatever page you are on, the source matters more than the description.

• Read the source. Entries like Bandcamp Purchases Export link to their source (a GitHub Gist in that case). Skim it before running it on pages where you are logged in.
• Match the script to the site. A script written for one service will usually do nothing useful elsewhere.
• Check what data it touches. Export-style scripts read page data and produce a file; know where that file goes and what it contains.
• Prefer entries with a visible source link over ones that only show a description.

Who it is for

Get Bookmarklets fits people who want a lightweight tool for a specific task — exporting a purchase history, for instance — and are comfortable dragging a bookmark and reviewing a short script. It is less suitable if you want vetted, maintained software with support, or if you are unwilling to inspect code before running it. The site does not present itself as a store; no pricing or account requirements are described in the available material, so treat access and any login conditions as things to verify on the site itself.

Bottom line

Use Get Bookmarklets as a discovery layer for small browser scripts: browse the catalog, open the entry you need, check its source, and install by dragging. The main decision is not whether the site is useful but whether the specific script's code is something you are willing to run in your browser.

Get Bookmarklets is a collection of browser scripts you can install with a single drag. To install a bookmarklet, drag its link from the site onto your browser's bookmarks bar; to install a userscript, you need a userscript manager extension, because the site's one-drag method applies to bookmarklets. The site describes itself as "browser scripts you can trust" and organizes content around "How it works" and "What, How, Why?" sections, with each script showing its source URL and source code.

What a bookmarklet actually is

A bookmarklet is a bookmark whose address is JavaScript instead of a web address. When you click it, the code runs in the page currently open in your browser tab — not on Get Bookmarklets itself. That distinction matters: the script acts on whatever site you are viewing when you click it, so the same bookmarklet can do different things depending on the page.

Because the code runs in your browser, you are trusting the script author with the content of the page you run it on. Get Bookmarklets addresses this by showing each script's source URL and a source code link, so you can read the code before installing.

Installing a bookmarklet by drag and drop

1. Show your bookmarks bar. Most browsers toggle it with a keyboard shortcut or a menu option; the bar must be visible for dragging to work.
2. Open the script's page on Get Bookmarklets and locate its install link.
3. Drag the link onto the bookmarks bar and release. A new bookmark appears.
4. Test it on a relevant page. Open a site the script is meant for, then click the new bookmark. The expected result is that the script runs on that page — for example, the Bandcamp Purchases Export script is designed to export your Bandcamp purchase history, so you would run it while logged in on Bandcamp.

If dragging does nothing, the usual causes are a hidden bookmarks bar, a browser that blocks the drag, or dragging to the page instead of the bar. Creating a bookmark manually and pasting the script's code as its address is the standard fallback.

Bookmarklets vs. userscripts

The site's single-drag installation applies to bookmarklets. Userscripts require the extra step of a manager extension, which is what lets them run automatically rather than on click.

Checking a script before you install it

Use the source code link on each script's page. For the Bandcamp Purchases Export entry, the page lists a source URL pointing to a GitHub Gist and a "Source code" link. Reading the code, or at least confirming the source host, tells you what the script does and where it came from before you drag it to your bar. The site also invites you to browse, share, and submit your own scripts, so quality and behavior can vary by author — the source link is your main check.

Common sticking points

• Nothing happens on click: you may be on a page the script does not support, or the script may require you to be logged in to the target site.
• The bookmark looks like a normal link: some browsers strip the javascript: prefix when you paste it manually; retype it if needed.
• You expected automatic running: that is userscript behavior, not bookmarklet behavior. Install a userscript manager for scripts meant to run on their own.

The site's materials do not state pricing for using the collection; the only pricing-related signal in the page data is the word "purchase," which appears in the name of the Bandcamp Purchases Export script, not as a site fee. Treat access terms as unconfirmed rather than assuming the site is free.

Get Bookmarklets presents its collection as "browser scripts you can trust," but that label is the site's own positioning, not an independent audit. The practical answer: a script from the site is only as trustworthy as its source code and the person or repository behind it. You can make a reasonable decision by opening the source link shown on each script's page, reading what the code actually does, and installing it only if you understand and accept that behavior. If you can't read the code or the source link is missing or unclear, treat the script as unverified.

What the site actually gives you

Get Bookmarklets describes itself as a collection of bookmarklets and userscripts you can install with a single drag, and it invites visitors to browse, share, and submit their own scripts. That means the catalog is community-contributed in nature — the site is a distribution point, not a publisher that vouches for each entry.

The site's own framing is worth reading literally. Its headings include "How it works" and "What, How, Why?", and the page positions the collection under the banner "Browser scripts you can trust." That is a claim about the site's intent and curation, not a guarantee about any individual script.

The source link is your main verification tool

The most useful trust signal on a script page is the source URL and the accompanying "Source code" link. The site's listing for Bandcamp Purchases Export, for example, shows a Source URL pointing to a raw file on gist.githubusercontent.com, plus a "Source code" link.

That pattern matters for three reasons:

• You can read the exact code before installing. The raw file is the script itself, not a description of it.
• You can see who hosts it. A gist or repository under a known account is traceable; an anonymous paste is not.
• You can check whether the hosted code matches what you'd install. If the page's install action and the source link point to the same file, there's less room for a swapped payload.

A script page without a working source link, or one whose source link leads somewhere unrelated to the script's stated purpose, is a reason to stop.

How to review a script before you drag it

You don't need to be a programmer to do a basic review, but you do need to look at the code. A workable routine:

1. Open the source link and read the whole file, not just the top.
2. Look for network calls. Search the code for fetch, XMLHttpRequest, or URLs. Ask: what data is being sent, and to whom? A script that exports your Bandcamp purchases legitimately needs to read your purchase pages; one that also posts data to an unfamiliar domain does not.
3. Look for credential or cookie access. References to document.cookie, localStorage, or tokens are worth understanding before you run anything.
4. Check the scope. A bookmarklet runs on whatever page you click it on. A userscript typically declares which sites it matches — a script that claims to work on one site but matches all sites deserves scrutiny.
5. Note what it modifies. Scripts that change page content or submit forms on your behalf can cause actions you didn't intend.

If after reading you can't explain in one sentence what the script does and what it sends where, don't install it.

General precautions for any third-party browser script

These apply to Get Bookmarklets and to every other bookmarklet or userscript source:

• Prefer scripts with a visible, attributable source. A named author and a public repository or gist are better than an anonymous file.
• Install userscripts through a manager you control, so you can see the script's declared permissions and disable or remove it later. A bookmarklet is just a bookmark, which makes removal easy but also means it runs with the full trust of the page you click it on.
• Test on a low-stakes account or page first, especially for anything that reads account data.
• Re-check after updates. If a script's source changes, the version you reviewed may no longer be the version you're running.
• Don't run scripts on sensitive pages — banking, email, or admin panels — unless you fully understand the code.

Making the call

Use the site as a catalog and the source links as your evidence. A script with a clear source URL, readable code, and a purpose that matches its behavior is a reasonable thing to try. A script with no source link, obfuscated code, unexplained network requests, or broad site matching is not — regardless of how the collection is described. The "you can trust" framing tells you what the site aims for; your own read of the source code tells you what you're actually installing.

Get Bookmarklets (getbookmarklets.com) is a collection of browser bookmarklets and userscripts you install with a single drag, and you can browse, share, and submit your own scripts. To find a specific script such as Bandcamp Purchases Export, browse the collection by purpose, open the script's listing to read its source URL and source code, then drag it to your bookmarks bar to install. The site describes its scripts as "browser scripts you can trust," but that is the site's own framing — you should still review the source before installing anything.

Browsing the Collection to Locate a Script by Purpose

The site is organized as a browsable collection rather than a search-first tool, so the practical approach is to scan listings for the task you have in mind. Each entry is presented with its name and a short description of what it does, which is usually enough to match a script to a job like exporting purchase history, cleaning up a page, or pulling data out of a service.

When you find a candidate, don't install from the browse view alone. Open the listing first — that is where the details you need to judge the script live.

Reading a Script's Listing Details

A listing on Get Bookmarklets gives you three things worth checking before you install:

• The script name and description — confirms the purpose matches your task.
• The source URL — where the script actually comes from. For the Bandcamp Purchases Export entry, the source URL points to a GitHub Gist raw file (gist.githubusercontent.com/...), meaning the code is hosted and versioned outside the site itself.
• The source code — the listing exposes the code so you can read it rather than trusting a black box.

That combination is what makes the site useful for evaluation: you can see both where a script originates and what it contains before it touches your browser.

What the Bandcamp Purchases Export Example Does

The Bandcamp Purchases Export entry is a concrete illustration of how a listing reads. Its source URL resolves to a raw JavaScript file on a GitHub Gist, and the listing links to the source code directly. In practice, a script with this name is meant to pull your Bandcamp purchase records out of your account into a file you can keep — useful if you want a personal archive of what you've bought.

Because the code is hosted on a Gist, you can also open the Gist page itself to see revision history and any comments, which gives you more context than the listing alone.

Installing a Bookmarklet or Userscript

The install model is the same across the collection: bookmarklets are installed by dragging, and userscripts are installed into a userscript manager.

1. Make sure your bookmarks bar is visible in your browser — bookmarklets live there.
2. Open the script's listing and locate the install link or the drag target.
3. Drag the link to your bookmarks bar. The browser saves it as a bookmark whose address is the script itself.
4. Run it on the right page. Navigate to the site the script targets (for the Bandcamp example, your Bandcamp purchases page) and click the bookmark.
5. Verify the result. For an export script, confirm a file was produced and that it contains the records you expected.

For userscripts, the equivalent step is installing a userscript manager first, then adding the script from its source URL.

Common Snags

• Nothing happens on click. Bookmarklets often only work on the matching site and page; running them elsewhere silently does nothing.
• The browser blocks or strips the script. Some browsers restrict javascript: bookmarks in certain contexts — check that the bookmark was saved intact.
• The script depends on the page's current layout. Export and scraping scripts break when the target site changes its markup, so a script that worked before may need an update.

Sharing or Submitting Your Own Script

The site accepts community submissions, so if you've written a bookmarklet or userscript, you can submit it to the collection for others to install with a single drag. Sharing works the same way in reverse: point people at the listing, and they get the description, source URL, and code in one place.

Deciding Whether to Trust a Given Script

Trust here comes from reading, not from the site's tagline. Before installing, open the source code and check what it sends where — look for network requests to domains you don't recognize, and confirm the script only does what its description claims. For scripts hosted on a Gist, check the author and revision history. If the code is obfuscated or you can't follow it, that's a reason to skip it. The one-drag install is convenient, but the review step is what actually protects you.