Best Gumroad Chrome Extensions (2026): Every One I Could Actually Verify

Updated 2026-07-27 · GumKit guides

Search "best Gumroad Chrome extensions" and the results are mostly Gumroad product pages about building Chrome extensions — a course on extension basics, a database of Manifest V2 extensions to rebuild, a scraped list of Web Store listings — plus one Amazon review-research tool and a generic "best Chrome extensions" roundup. The query matches on the words, not the intent. Nobody has actually sat down and compared the extensions that work on Gumroad.

Part of the reason is that there isn't much to compare. A Chrome Web Store search for "gumroad" returns seven Gumroad-specific extensions, most with double-digit install counts, and at least one popular recommendation has quietly disappeared. That's the honest shape of it.

I make one of these tools, so treat the recommendations accordingly. What I can offer instead of neutrality is verification: every number below came from loading the actual Chrome Web Store listing on July 27, 2026, and every claim about Gumroad's API came from reading Gumroad's open-source codebase. Where I couldn't verify something, I say so instead of filling the gap.

What's actually on the Chrome Web Store

Here is every Gumroad-specific extension the Web Store search returns, each one loaded and confirmed. Install counts and ratings are what the listing displayed on the date above; these numbers drift, and the Web Store rounds them, so treat them as a snapshot rather than a constant.

Yes, GumKit has three users, the smallest count on the list. I'm not going to dress that up — if social proof is what you're shopping for, the bottom row is the wrong row.

Two things jump out of that table. First, nothing here has meaningful review volume. The highest rating count is two. Any "top rated" framing in this category is noise. Second, the most-installed extension isn't a seller tool at all — Gumroad Bulk Downloader is for buyers, grabbing every file from a purchase page at once. It has more installs than the other six combined, and it's completely irrelevant if you're the one selling.

The three jobs these tools actually do

Once you strip the marketing copy, the seven extensions split cleanly into three groups that barely overlap. Knowing which group you need eliminates most of the decision.

Reading other people's stores. Gumroad Scraper and G-Digital Scraper both work by extracting data from Gumroad pages you visit — Discover search results, product pages, seller profiles. You're doing market research: what's selling, at what price, with what review counts.

Reading your own numbers. AY Seller Dashboard+ and the web app fullstats.io both connect to your own account and build charts on top of it — revenue over time, refunds, top products.

Changing your own store in bulk. This is where GumKit sits, and it's the smallest group. Gumroad's dashboard makes you edit products one at a time; bulk tools batch those edits.

Gumroad Exporter, Gumroad Bulk Downloader and Bulk Saver for Gumroad are one-job utilities that sit off to the side — catalog dump, and file download twice over. Bulk Saver and Bulk Downloader do the same buyer-side job: scan a purchase page, list the files, queue the downloads. Bulk Saver adds retries, download history and a custom subfolder; Bulk Downloader has roughly seventy-five times the installs. Neither has anything to do with selling.

The feature matrix

The axis that matters most isn't features, it's where the data comes from, because that determines what the tool can do, what it can break, and what happens when Gumroad changes its HTML. The two file-downloaders are left out here — they move files off a purchase page and produce no dataset to compare.

Sources: each tool's Chrome Web Store listing, fullstats.io, and the Gumroad OAuth authorize URL fullstats uses, which requests scope=view_sales — read-only. That's a genuinely good sign in a tool you're handing your sales history to, and it's the kind of thing you can check yourself before clicking Authorize: read the scope parameter in the URL bar.

Gumroad's scope list isn't in the public docs in full, but it's right there in the source, and it comes in two versions. config/initializers/doorkeeper.rb declares default_scopes :view_public and then seventeen optional_scopes: edit_products, edit_emails, view_sales, view_payouts, mark_sales_as_shipped, refund_sales, edit_sales, revenue_share, ifttt, mobile_api, creator_api, view_profile, edit_profile, unfurl, helper_api, view_tax_data, account.

The same file also defines a shorter public_scopes list — the ones "the public should be aware of," per its own comment — which drops mobile_api, creator_api, unfurl and helper_api, and also omits refund_sales. So a scope existing in optional_scopes doesn't mean you'll ever see it offered on a consent screen. What's useful to you as a buyer of these tools is the read: if a tool asks for account when it only needs to read sales, that's over-reach worth questioning.

Scrapers and the terms of service

This is the part most comparison posts skip, and it isn't a small footnote.

Gumroad's Terms of Service, Section 14, prohibits users from using

"any manual or automated software, devices or other processes (including but not limited to spiders, robots, scrapers, crawlers, avatars, data mining tools or the like) to 'scrape' or download data"

That language is about as direct as it gets, and it names scrapers explicitly. Both Gumroad Scraper and G-Digital Scraper are, by their own descriptions, exactly that. Worth noting that the clause says nothing about whose pages — Gumroad Exporter and the two file-downloaders read pages too, they just read your own. That's a much easier argument to make, but it isn't a different mechanism.

I won't predict what happens to you, because I don't know. There's no public record of Gumroad suspending sellers over competitor research, and running one of these extensions is not the same as hammering the site with a server-side crawler. But the clause exists, and you should make that call knowing it's there. If you use one, use it at human pace on pages you'd have browsed anyway.

The API-based tools sit on the other side of that line: they use credentials Gumroad issues you, hitting endpoints Gumroad publishes, subject to Gumroad's own rate limits. That's a meaningfully different posture.

What Gumroad's API lets a tool do — and what it doesn't

Every API-based tool on this list is working inside the same box, and the box has hard walls. Reading the API v2 controllers tells you more about what's possible than any marketing page will.

Sales come back ten at a time. In sales_controller.rb, the constant is RESULTS_PER_PAGE = 10. Not 100, not 1,000. Ten. So a 2,000-sale export is 200 sequential HTTP requests, each returning a next_page_key you feed into the next one. This single number explains why every "export my customers" tool takes a while on an established account, and why none of them are instant.

The page parameter is deprecated, but not disabled. The source marks it # DEPRECATED and the deprecation notice you'll see quoted around the web —

The 'page' parameter is deprecated. Please use 'page_key' instead: https://gumroad.com/api#sales

— is not what a page request normally returns. Read the controller: that string is the rescue for a QueryTimeoutError. Gumroad wraps the offset query in a timeout (15 seconds by default, adjustable at runtime through Redis) and only swaps in the deprecation message when the query blows past it. On a small account, page still works and returns sales. What actually happens is that offset pagination gets slower the deeper you go, and past some depth it starts failing — with a message that blames the parameter rather than the timeout. Either way, a tool still built on page numbers is one you should assume will break on a big catalog.

One throttle touches this endpoint, and it probably isn't yours. rack_attack.rb does contain throttle("/api/v2/sales", limit: 10, period: 1.second) — but read the block it's given, not just the name:

throttle("/api/v2/sales", limit: 10, period: 1.second) do |req|
  req.remote_ip if req.path.ends_with?("/v2/sales") && req.params["page"].to_i > 10
end

The rule returns a throttle key only when page is present and above 10 — Gumroad's own comment on it reads "Throttle requests to Sales API with slow pagination." Paginate with page_key and the parameter this rule inspects is never present, so it never fires. It gets misquoted constantly as "the Gumroad sales rate limit"; it isn't one. The rules that do bind a bulk job live elsewhere in that file and get their own post: what actually triggers a Gumroad 429.

There is no followers endpoint. The v2 controller directory holds 28 files and folders; set aside the shared base_controller.rb and the remaining 27 are sales, links (products), offer codes, variants, variant categories, subscribers, payouts, earnings, custom fields, licenses, upsells, refund policies, resource subscriptions, skus, thumbnails, covers, media, files, pages, emails, categories, bundle contents, direct uploads, tax forms, users, Notion unfurl URLs, and a walks subdirectory. No followers. So when I say GumKit can't export your followers, that's not a roadmap gap — no API tool can, because Gumroad doesn't expose it. subscribers covers membership subscriptions, which is a different thing.

Discount codes are percent-off or amount-off, and the parameter is not a strict enum. offer_codes_controller.rb has a single branch: if params[:offer_type] == "percent" it sets amount_percentage, and the else sets amount_cents. That else catches everything. Send offer_type: "cents", send offer_type: "fixed", send nothing at all, and you get the same result — a fixed-amount discount in the product's currency. Nothing rejects an unrecognized value, which means a typo in the word percent silently ships a dollars-off code where you wanted a percentage. "percent" is the only string that changes the outcome. There's also a minimum_amount_cents parameter, accepted on create and one of only two fields (with max_purchase_count) that update will permit you to change afterwards.

Webhooks do exist — resource_subscriptions_controller.rb — and they're bound to the OAuth application that created them, which means an extension using a personal access token rather than a registered OAuth app has no natural place to hang them. GumKit doesn't use them at all, which is the honest reason it has no auto-sync.

If you want the full field-by-field breakdown of what a sale object contains and how it differs from the dashboard's CSV button, that's a separate piece: Export Gumroad Customers to CSV.

What GumKit does, and a worked example

GumKit has four tabs, and that's the whole product: Discount codes, Prices, Listing SEO, and Customer CSV. It talks to api.gumroad.com with an access token you generate yourself and paste into the options page. There's no GumKit server, no account, and no signup — the manifest requests only storage and alarms, and its host permissions are api.gumroad.com and api.openai.com (the latter only for the SEO tab, using your own key). It has no content scripts at all, meaning it never reads or touches a Gumroad page in your browser. Free, with no paid tier.

The part worth explaining is the pacing, because it's the difference between "bulk tool" and "way to get rate-limited."

Every bulk write — price change or discount code — goes into one queue that spaces requests 2,400 ms apart, about 25 a minute. That number is set by the tighter of the two paths: price changes are PUT /v2/products/:id, which rack_attack.rb caps at 30 per 60 seconds, keyed by IP and by access token. Discount codes post to a different path with no rule of its own, and inherit the same pacing anyway (the full rule set). So applying one code across 60 products is 60 queued writes at 2.4 seconds each: roughly two and a half minutes, not instant. On a 429 the queue waits and retries the same item up to 8 times before marking it failed and moving on, so one bad product doesn't kill the run — and since Gumroad never sends a Retry-After header, that wait is always the 30-second fallback.

Reads are paced at 350 ms. Nothing on the page_key path throttles them, so this is politeness rather than compliance. Combine it with ten sales per page and you can predict your own export: 2,000 sales = 200 pages ≈ 70 seconds of pacing alone, plus network time. There's also a hard stop at 500 pages, so a single export tops out around 5,000 sales; past that you slice it with the date filters.

The CSV itself derives its columns from the union of every key Gumroad returns, rather than a fixed list, so new fields show up automatically instead of being silently dropped. It ships a UTF-8 BOM so Excel doesn't mangle non-English buyer names, and prefixes any cell whose first non-whitespace character is =, +, -, or @ — leading spaces included, since Sheets trims them before deciding a cell is a formula — so a malicious product title can't execute when you open the file.

Closing the popup doesn't stop a job — the queue lives in the service worker and keeps going.

Getting the token is the one genuinely fiddly step, and it's not where you'd expect in the settings UI: Gumroad API Access Token walks through it.

What GumKit can't do

This is the section I'd want to read first if I were you.

A few of those deserve more than a table row. Bulk-deleting discount codes is the one I get asked about most: the delete call is written and sitting in the codebase, but it isn't wired to any button, so it does not exist as a feature you can use. Saying "it's built, just hidden" would be a weasel — as far as you're concerned, it isn't there. The same goes for editing an existing code.

No line-by-line preview needs a precise description, because there is a confirmation. Hit go and you get a browser dialog with the count and a time estimate — "Change prices on 42 products. This will take about 2 min (rate limit ~25/min). Proceed?" — and nothing runs until you accept. What you don't get is the list: no screen showing "$29 → $19" for each of the 42 before you commit. Those old-and-new prices are computed, and they scroll past in the progress log while the job runs, but you see them after the write, not before. If that gap makes you nervous, deselect everything but two products and run it once.

And GumKit shows you nothing about your business. No charts, no trends, no revenue summary. It changes things and it exports things. If what you actually wanted was to understand your numbers, it's the wrong tool and one of the analytics options above is the right one.

Which one should you install

The honest summary: if you're a researcher, the scrapers are your category and the ToS clause is your judgment call. If you're an analyst, fullstats.io is the most mature thing here by a distance — it's a real web app with continuous sync, not a browser popup. If you're an operator with more than about twenty products and you're tired of editing them one at a time, that's the narrow slot GumKit fills.

Tools I couldn't verify

One name that recurs in Gumroad-extension discussions didn't survive checking, and leaving it out silently would be the dishonest move.

GumView. An analytics overlay — sales counts and review data drawn onto Gumroad's own pages — sold at zexo.gumroad.com/l/Gumview. As of July 27, 2026, that URL returns a 404, and so does the seller's entire store page at zexo.gumroad.com. I checked with a normal browser user-agent to rule out bot-blocking; fullstats.io returned 200 in the same pass, so it isn't my end. GumView also doesn't appear in a Chrome Web Store search for "gumroad" — that search returns the seven extensions in the table above and nothing else Gumroad-specific. Search engines still index the product page, still titled "$40 a year," but the page behind that result is gone, so I won't build a price or a feature row out of a cached snippet. Best available conclusion: it's gone. If you find a working install link, it's not the one everyone is citing.

I also didn't put dollar figures on the paid options. fullstats.io prices in bands by your monthly revenue — under $300/month is listed as free, and the tiers above it say "We provide custom prices based on your needs" instead of a number. AY Seller Dashboard+ refers to a "PRO" upgrade covering Excel/CSV export and customer-lifetime-value analytics, without listing a price on its Web Store page. Quoting a number I can't see would be making one up.

FAQ

What is the best Gumroad Chrome extension?

There isn't one, because the tools don't compete — they do different jobs. For competitor research, Gumroad Scraper or G-Digital Scraper. For your own analytics, AY Seller Dashboard+ or the fullstats.io web app. For bulk-editing your store, GumKit. For pulling files out of something you bought, Gumroad Bulk Downloader or Bulk Saver for Gumroad. Install counts across the entire category top out at 302, and no extension has more than two ratings, so ignore any "top rated" claims.

Are Gumroad scraper extensions against the terms of service?

Gumroad's Terms of Service, Section 14, explicitly prohibits using "spiders, robots, scrapers, crawlers... or the like" to scrape or download data. That language covers the scraper extensions on this list. Whether Gumroad enforces it against a seller doing light competitor research is unknown — there's no public record either way — but the clause exists and you should decide with it in front of you.

Does Gumroad have an official Chrome extension?

No. Every extension in this comparison is third-party. GumKit is independent and is not affiliated with, endorsed by, or sponsored by Gumroad.

Can any extension export my Gumroad followers?

No, and none ever will through the API. Gumroad's API v2 has no followers endpoint — you can confirm this by listing the controllers in the open-source repo. Only a page-scraping tool could attempt it, which puts you back in the terms-of-service problem.

Why do Gumroad export tools take so long on big accounts?

Because the sales endpoint returns ten records per request (RESULTS_PER_PAGE = 10 in Gumroad's source), and pages must be fetched sequentially: each response hands you a next_page_key you need before you can ask for the following page, so they can't be run in parallel. Five thousand sales is five hundred round trips, one after another. The commonly cited "10 requests per second" limit on this endpoint only applies to the deprecated page parameter above page 10 and doesn't touch cursor pagination — the throttle rules in detail.

Is it safe to give an extension my Gumroad API token?

It depends entirely on where the token goes. A token stored locally and sent only to api.gumroad.com is a very different risk from one relayed through a third-party server. Check the extension's host permissions before installing, and prefer tools that request the narrowest OAuth scope for the job — view_sales for anything read-only. You can revoke a token at any time from Gumroad's settings, which is the real safety net.

The takeaway

The category is thin. Seven verifiable extensions, no meaningful reviews, one widely-recommended tool that has vanished, and a hard ceiling on what any of them can do set by Gumroad's own API — ten sales per page, no followers endpoint, one branch in the discount code logic.

That thinness is useful information. You don't need a shortlist of fifteen; you need to answer one question — am I researching, analyzing, or editing? — and install the one tool for that job. Be skeptical of any post here presenting a ranked list with star ratings, because the data to build one doesn't exist.

GumKit is my answer to the third question only, it's free, and I've tried to be specific above about the several things it won't do for you. If your problem is one of those, one of the other tools on this page is the better install.