Ebook stamping means marking each copy you sell with something that ties it to the person who bought it: a visible line on the page, a hidden identifier in the file, or both. The reader can still open the book on any device. The point is deterrence and traceability, not a lock. If you sell ebooks in the US and want fewer copies passed around, stamping is the lightest option that still gives you something to act on when a file turns up where it shouldn't.
This guide covers what stamping does and does not do, what belongs in the stamp, how PDFs differ from EPUBs, the privacy and legal points US creators should know, and a workflow you can follow this week.
TL;DR
- Stamping (also called watermarking or "social DRM") embeds buyer-specific information in each copy. It does not encrypt the file or restrict which device can open it.
- It discourages casual sharing and lets you trace a leaked copy to its original purchase. It cannot stop a determined person from copying a file.
- Use an opaque identifier or order ID rather than a full name, email or phone number, and tell buyers what the stamp contains.
- A stamp on a PDF should be kept out of the tag structure and checked for legibility so it doesn't hurt accessibility.
- Pair stamping with secure delivery, download limits and sensible pricing. Protection works best as a set of small measures.
Table of Contents
- What ebook stamping actually is
- Visible and invisible stamps
- Stamping versus DRM
- What stamping can and cannot do
- What to put in the stamp
- Stamping PDFs without hurting accessibility
- US legal points to know
- A practical workflow for creators
- Other ways to reduce sharing
- Our perspective
- Sell your ebooks with secure delivery
- FAQ
- Sources
What ebook stamping actually is
The term sounds like a craft hobby, and a search for it mostly returns rubber stamping and metalworking books. In digital publishing it means something else: adding buyer-specific information to an ebook at the moment of sale. Industry coverage of social DRM describes it as embedding purchaser information in the file, in contrast to DRM, which encrypts a file to limit usage to particular devices or apps.
The same idea goes by several names:
- Ebook stamping: usually a visible mark, such as a line in the footer or on the title page.
- Watermarking: can be visible or hidden, and is the word most people type when they want to prevent ebook sharing.
- Social DRM: the label for the whole approach, based on the idea that people think twice before sharing a file with their name on it.
Whatever you call it, the mechanism is the same. Each sale produces a slightly different file. The difference is the stamp.
Visible and invisible stamps
You have two ways to mark a copy, and many sellers use both.
Visible stamps
A visible stamp is text a reader can see: "Licensed to order #48213" on the copyright page, or a discreet footer on every page. Its job is psychological. A buyer who sees an identifier on every page is less likely to upload the file to a forum or send it to twenty friends.
Placement matters. A stamp across the middle of a page in grey capitals irritates paying readers and does little extra. A line on the copyright page plus a small footer is usually enough, and it keeps the reading experience clean.
Invisible stamps
An invisible stamp hides an identifier inside the file, where the reader never sees it. If a copy later appears on a file-sharing site, you extract the identifier and match it to an order. According to the same industry overview, publishers often combine this with copyright-monitoring services that scan the internet for leaked files.
Hidden marks have a weakness: they are only useful if they survive. Converting a file, stripping metadata or re-saving it can destroy the identifier. That is why a visible stamp alongside a hidden one is the more robust choice. If one gets removed, the other may remain.
Stamping versus DRM
Creators often treat the two as the same thing. They are not, and the difference decides which one suits your readers.
DRM encrypts the file and restricts usage, for example by limiting which devices can open it or blocking copying and printing. Stamping leaves the file open: per the social DRM overview, it stays usable on any device or app that supports the format.
| Stamping (watermarking) | Traditional DRM | |
|---|---|---|
| How it works | Adds buyer-specific information to each copy | Encrypts the file and ties access to devices, apps or accounts |
| Reader experience | Opens anywhere the format is supported | Can require an extra app, account or device authorisation |
| Stops copying? | No, it deters and traces | Raises the effort needed, but is not unbreakable |
| Evidence after a leak | Identifies the original purchase | Usually none |
| Support burden | Low | Higher: activation errors, device limits |
| Best for | Ebooks, workbooks, guides sold directly to fans and students | Content where tight access control justifies the friction |
If you want to see what DRM friction looks like for readers, our explainer on e-book DRM and Adobe device limits walks through the activation and device-cap problems that make many buyers abandon a purchase. For educational products, where you want the buyer to actually finish the material, that friction is often the bigger cost.
What stamping can and cannot do
Be honest with yourself about this before you spend time on it.
What it can do
- Discourage casual sharing. According to the social DRM overview, a link between a file and its purchaser may put people off sharing with their name attached.
- Give you a trail. If a stamped file shows up on a sharing site, the identifier can lead you to the original order.
- Support a takedown or a conversation with the buyer. A traced copy turns "someone leaked it" into "this licence was shared".
What it cannot do
- Stop a determined person. The same source is clear that stamping does not physically restrict copying or distribution the way DRM attempts to.
- Work without protection around it. One security vendor's analysis makes the point that a watermark is only as strong as the file's copy protection, and that combining it with DRM can be potent. For most small creators that combination costs more in reader goodwill than it returns, but it is worth knowing the limit.
- Replace a good offer. Piracy tends to thrive where legitimate access is expensive, inconvenient or unavailable in a buyer's region or currency.
A realistic goal is to make the honest choice the easy one and the dishonest one slightly uncomfortable. Stamping does that.
What to put in the stamp
This is where many creators go wrong. The temptation is to print the buyer's full name, email address and phone number on every page, because it feels like the strongest deterrent. It also creates problems.
- A readable email address on every page exposes the buyer if the file is shared in good faith, lent to a colleague or opened on a shared screen.
- It turns your product into a store of personal data that travels with the file, outside your control.
- It can feel hostile to the people who paid you.
According to the social DRM overview, a watermark payload can be obfuscated: an alphanumeric identifier, a user ID or an encrypted email address. That is the better pattern. You keep the lookup table in your own order system, and the file carries only a code that means nothing to anyone else.
A sensible stamp has three parts:
- A short visible line, such as "Licensed to the original purchaser, order ID 48213".
- An opaque hidden identifier that maps to the same order.
- A plain-language note on your product page or checkout saying that each copy is individually marked, and what the mark contains.
The third point protects trust. Buyers rarely object to a stamp they were told about, and many appreciate a licence note that explains what they may and may not do with the file.
Privacy habits worth adopting
Treat the identifier like any other piece of customer data: collect only what you need, keep it only as long as you need it, and say what you do with it. US regulators have repeatedly stressed data minimisation. The FTC, in an order notice from 2024, described data-minimisation measures as important for reducing the risk of misuse. That case concerned location data, not ebooks, but the principle carries over: if the stamp doesn't need an email address, don't print one.
Also keep your promises. The FTC has treated failure to honour privacy commitments as deception, as in its commissioners' statement on a 2000 case. If your checkout says you will not share buyer data, a stamp that publishes it in the file would contradict you. For your own situation, a US attorney who handles privacy or e-commerce can confirm what your terms and checkout notices should say.
Stamping PDFs without hurting accessibility
PDF is the most common format for workbooks, guides and course companions, and it is also where a careless stamp does the most harm.
Two cautions from accessibility guidance:
- Norfolk County Council's PDF accessibility guidance recommends avoiding watermarks because they are usually difficult to see. Low-contrast diagonal text across a page is hard for low-vision readers and can obscure content.
- The accessibility consultancy BOIA, in its list of common PDF mistakes, advises against putting watermarks or other non-essential elements into the tag tree. Tagged content is what screen readers announce, so a stamp that sits in the tags gets read aloud on every page.
For educational publishers, who often serve students with accessibility needs, the practical rules are:
- Keep visible stamps small, high-contrast and in the footer or on the copyright page, not over the body text.
- Make sure the stamp is marked as an artefact (decorative, non-content) rather than real content, so screen readers skip it.
- Open the stamped file with a screen reader or an accessibility checker before you ship the process to customers.
- Rely on the hidden identifier for traceability, and use the visible one only as a gentle reminder.
EPUB is more forgiving, because it reflows text and a stamp can live on the title or copyright page. Many readers prefer it for long-form content for that reason.
US legal points to know
Stamping touches copyright law in two ways, and neither requires you to be a lawyer to grasp the basics.
Your stamp can be copyright management information. The DMCA defines this kind of information broadly, including details that identify a work, its author or its rights holder, in 17 U.S.C. § 1202(c) as summarised by a law firm. Putting your name, the title and a copyright notice in the stamp, in addition to the buyer's order code, can therefore give you more to point to if someone strips it. Whether a specific removal is actionable depends on the facts, so take advice before sending a demand.
Registration is a separate step. A stamp does not register your copyright. If you want the strongest position for enforcement, registration with the US Copyright Office is the route, and its registration process overview is the place to start. It also advises applicants not to supply private or confidential information that registration does not require, a good reminder not to paste buyer data into any filing.
If you need to send a takedown notice or consider a claim, speak to an intellectual property attorney in your state. A stamp gives you evidence. A lawyer tells you what to do with it.
A practical workflow for creators
Here is a sequence that works for most independent educators, authors and course creators.
- Decide what you are protecting. A $9 checklist and a $149 professional workbook justify different levels of effort. Lightly stamp low-priced items and add more layers to high-value ones.
- Choose the stamp content. Opaque order ID, your name and a licence line. No full email, no phone number.
- Pick the format. EPUB for reading-heavy books, PDF for workbooks and templates. Remember that PDFs need the accessibility checks above.
- Automate it. Manual stamping works for ten sales and collapses at a hundred. Use a delivery tool or script that generates the stamped copy at checkout.
- Tell buyers. One sentence on the product page: "Each copy is marked with an order ID."
- Limit the downloads. Combine stamping with expiring links and download caps so a single purchase can't be fetched endlessly. Our six-step guide to locking downloads covers this layer.
- Test before you publish. Buy your own product, open it on a phone, an e-reader and a desktop, run a screen reader over the PDF, and confirm the identifier traces back to the right order.
- Plan your response. Decide in advance what you will do when a leak turns up: a polite email to the buyer, a takedown request, or nothing at all for a small one.
Educational authors sometimes begin with a draft and only think about protection at the end. If you are still shaping the manuscript itself, for instance a book for young readers, a children's book publishing workbook can help you plan the content before you decide how the finished file will be marked and delivered.
Worked example: a pricing-aware approach
Suppose you sell a 120-page budgeting workbook as a PDF at $19 and an accompanying template pack at $29. You decide that the workbook gets a footer stamp ("Licensed to order #48213, do not redistribute") plus a hidden ID, marked as an artefact for screen readers. The template pack, which buyers will edit and reuse, gets only a licence note on the first sheet and an expiring download link, because heavy stamping would get in the way of use.
That split is the principle in miniature: protect proportionally to the damage a leak could do, and never at the cost of the buyer's ability to use what they bought. If you are unsure how much to charge in the first place, our guide to pricing educational ebooks shows how price shapes both sales and the temptation to share.
Other ways to reduce sharing
Stamping is one tool. Others worth combining with it:
- Fair pricing and bundles. A fairly priced product that includes updates, templates or a community gets bought rather than borrowed.
- Access, not just files. Courses, quizzes, live sessions and mentoring can't be copied into a single PDF. The more your product is an experience, the less a leaked file matters.
- Local payments. Buyers who can't pay with the method they have will look for free copies. Offering familiar payment options removes that reason.
- Fast, reliable delivery. An instant download that works first time beats a hunt for a leaked version.
- Clear licensing. State whether a book may be used by one person, a family or a classroom, and what a team licence costs.
For a wider view of getting educational material to readers, see our digital publishing guide for educational materials.
Our perspective
We build a marketplace for people who sell knowledge, and we see the same pattern in how creators think about protection: they worry about the one buyer who shares a file, and they overlook the dozens who abandoned checkout because the experience was difficult.
Our view is that stamping fits educational content better than heavy DRM. A learner who paid for a guide wants to open it on a laptop at work, a tablet on the train and a phone in a queue, and a licence note with an order ID asks for nothing in return. Heavy device limits turn a purchase into a support ticket.
We also think protection should not be an expensive commitment. That is why we charge no monthly fee and take a fee only when you make a sale: you shouldn't pay a fixed cost to protect a product that hasn't earned anything yet. Combined with secure, instant digital delivery and payment options buyers already use, the sensible stack is simple: a clear licence, a light stamp, limited download links, and a product good enough that buying it feels better than borrowing it.
No technique will stop every leak. Aim for fewer leaks, better evidence when one occurs, and buyers who feel respected.
— BibliOWLteca
Sell your ebooks with secure delivery
If you are ready to sell ebooks, courses, templates or other digital downloads, BibliOWLteca gives you a storefront, secure digital delivery and global payments without a monthly subscription. The Creator Plan has no published price, and the transaction fee starts from 0.99 EUR per sale, so you can see how it works on the pricing page before you commit. You can also browse the ebook, course and template categories to see how other products are presented.
When you set up your first product, decide on your stamp content and licence wording first, so your product page and delivered file say the same thing.
FAQ
Is ebook stamping the same as DRM?
No. DRM encrypts a file and restricts how, where and on which device it can be used. Stamping adds information about the buyer to the file and leaves it usable on any compatible device or app. DRM aims to prevent copying, while stamping aims to deter sharing and trace leaks.
Can a watermark stop people sharing my ebook?
Not completely. A watermark discourages sharing because the file carries a link to the buyer, and it helps you identify the source of a leak. A determined person can still copy the file, so stamping works best alongside limited download links, fair pricing and a clear licence.
What should I put in an ebook watermark?
Use an opaque identifier, such as an order ID, rather than a full name, email or phone number. You keep the lookup table privately, and the file carries only a code. Add your own name and a short licence line, and tell buyers at checkout that each copy is marked.
Do watermarks make PDFs harder to read for people with disabilities?
They can. Low-contrast text over the page is difficult to see, and a stamp left in a PDF's tag structure can be read aloud by screen readers on every page. Keep stamps small and high-contrast, mark them as artefacts, and test the file with a screen reader or accessibility checker before selling it.
Should I register my copyright if I stamp my ebooks?
Stamping and registration do different jobs. A stamp identifies a copy and its buyer, while registration with the US Copyright Office strengthens your legal position if you need to enforce your rights. An intellectual property attorney can tell you whether registration makes sense for your book.
Sources
- Everything you need to know about Social DRM for ebooks
- How to make PDFs accessible: layout and visual reading order (Norfolk County Council)
- 6 Common PDF Accessibility Mistakes (BOIA)
- Overview of the Registration Process (US Copyright Office)
- Copyright Management Information (Troutman Pepper Locke)
- FTC: InMarket order, respondents email notice (2024)
- FTC: ReverseAuction.com statement of commissioners (2000)