There is no Receiptify library.
There are three jobs.

what you are assembling

Nobody publishes a package that builds a Receiptify-style Spotify receipt, because a receipt generator is not one problem. It is three, and they are wildly unequal. Job one: get the listening history out of Spotify, which means OAuth, one endpoint, and a quota policy that decides whether the app can ever have users. Job two: draw a page that looks like till paper. Job three: turn that page into a PNG the user can post.

Jobs two and three are a weekend and are solved several different ways, compared further down. Job one is the entire difficulty of the project, and almost every tutorial on this topic ends before reaching it. Anyone deciding what to build should read the quota section first, because it determines whether the other two are worth starting.

where Tearline sits

Tearline is jobs two and three in one custom element, and has nothing to do with job one. That is worth saying plainly at the top rather than at the bottom: it removes the easy work, not the hard work. If the Spotify side does not clear, no rendering library rescues the project.

receipt.html

Jobs two and three, complete. The markup stays real text in the light DOM, so the track titles are still selectable and still read in order by a screen reader, and the PNG is produced in the browser with no server. The rest of the API is in the reference.

approach · what you write · trade

the failure everyone hits

Album art is the reason most first attempts export a receipt with holes in it. Four of the five approaches above rasterise in the browser, and the browser will not let a canvas holding cross-origin pixels give them back: drawing cross-origin data without CORS approval taints the canvas, after which toBlob() and toDataURL() throw instead of returning. Spotify's image CDN is a different origin, so covers pulled straight from the API trip it.

The fixes are to proxy the images through your own origin, to inline them as data: URIs before exporting, or to design a receipt that uses type instead of artwork — which is what actual till paper does. The mechanics, the second failure mode that looks identical but is not, and today's npm figures for the packages named above are all at export a DOM element as a PNG. The look itself — the monospace grid, the tabular figures, the torn edge — is given away in copyable CSS at receipt-style UI on the web.

three routes that survive the cap

Build it for five people and stop pretending otherwise. A development-mode app is a perfectly good personal tool, and Spotify says as much — it describes the mode as suited to apps built for accessing data in a single account. Add the five allowed users by hand, ship it as a thing you and your friends use, and skip the landing page.

Or take the data from the user instead of from the API. A paste box, a CSV upload, or a file from a personal-data export removes OAuth entirely, which means no quota mode, no Premium requirement on the owner, no five-user ceiling, and no access token to store. The receipt is identical. This is the route that scales for an individual, and it is under-built relative to how many people want one.

Or make a receipt of something that is not Spotify. The format carries anything with rows, a total and a date: a month of expenses, a workout log, a reading list, a git history, an order confirmation. None of those have a gatekeeper, and the rendering and export work is the same work.

if you want the render half done

Tearline is the second and third jobs as one tag. Load one file, wrap your rows in <tear-line>, and it renders as the paper — torn edge, dashed rules, seeded barcode — and exports itself with download(). Zero dependencies, no build step, MIT. It makes no claim about the Spotify half and never will.

The playground on the home page edits a live receipt in the browser, and the documentation has every attribute and method. Everything on this page is also buildable from scratch, and both linked write-ups exist so that it can be.

checked 2 August 2026

what is deliberately not here

No ranking of the receipt-generator sites currently serving this query, and no claim about which of them is the original. Several are running on domains that did not exist when the genre started, their operators are not identifiable from the pages themselves, and a ranked list assembled from search results would be a guess wearing a table's clothes.

Quota policy is the fastest-decaying claim on this page — it changed for individuals in May 2025 and can change again. Both figures above carry the date they were read, and the Spotify documentation is the authority, not this page. The cross-origin canvas behaviour in the export section is browser security rather than policy and moves far more slowly; it is sourced to MDN on the export page.