--- title: Sell an eBook with Tapmy description: "Step-by-step guide to selling an eBook with Tapmy: prepare the file, write the sales page, set free or paid access and test delivery as a buyer." lead: - To sell an eBook on Tapmy, upload a tested final file and cover, write a page that says who it is for and what they get, set free or paid access, then buy it yourself as a test. You can add the eBook component on all plans. tags: - digital-products source: docs/tapmy-wiki/pages/sell-an-ebook-with-tapmy--255af709.md --- **Applies to:** creators selling a guide, workbook, report or book as a digital product through the eBook component. ## What do I need ready? {#before-you-start} Gather the edited manuscript, a licensed cover, the final export, a contents list, your copyright and usage terms, any app readers need, your price or free-access choice, your refund policy and a support contact. Back up the source files and note which version is live before you replace anything. Use your own or properly licensed content, and test with throwaway buyer identities. ## How do I publish an eBook offer? {#publish-a-complete-ebook-offer} An eBook is more than a PDF upload. Before buying, people should know the topic, format, length, what they need to open it, what the license allows and what is not included. 1. Finish the manuscript and review facts, rights and privacy. Remove tracked changes, comments and private metadata. 2. Export a widely readable format that the Tapmy eBook flow accepts. Check headings, table of contents, links, images, fonts, selectable text and accessibility. 3. Create the eBook offer. Write the title, who it is for, the problem it solves, the outcome, contents, format, requirements and what is left out. 4. Upload the tested file and the cover. Record the version number. 5. Choose free or paid. For a paid eBook, connect Stripe and check that payments are ready before you publish. See [Pricing](/pricing) for plan details. Tapmy takes no fee on Free, 3% of your sales on Pro and 1% on Max. Standard payment processing fees from Stripe still apply, as they do on every platform. 6. Add the price, currency, refund policy, license and support details. Do not promise results the book cannot guarantee. 7. Preview the sales page on a phone and signed out, then claim or buy the eBook as a test and open the file you receive. 8. Check the customer and order record, and decide how you will release future editions. ## How do I know it works? {#what-success-looks-like} A reader who fits your audience understands what the eBook covers, completes the free or paid flow, receives the right edition and can open it on the device or app you named. Your records match the transaction. Test signed out and, where access matters, with a separate buyer identity. A live sales page alone does not prove delivery works. ## What if something is wrong? {#troubleshooting-and-limits} - **The file will not open on some devices.** Export again in a more compatible format and say which app or format readers need before checkout. - **The cover or text is blurry.** Fix the source export. Do not stretch a low-resolution image or a rasterized page. - **Buyers get an old edition.** Check the attached file, version, publication state and cache before uploading again. Check the product screens for supported eBook formats, file size and download limits. Do not claim copy protection or lifetime access unless you have confirmed it. If a buyer may already have paid, do not charge again, delete the order or remove access while you investigate. Save order, buyer, product and timestamp details first, with private data removed. ## What next? {#next-steps} After the buyer test, feature the eBook in your mobile store layout and set up a routine for announcing corrected or expanded editions. If delivery still fails, [contact Tapmy Support](/help/tapmy-support) with the public offer URL, the buyer's checkout email, an order or receipt reference if you have one, the exact time and time zone, what you expected and screenshots with private data removed. Never send passwords, codes, full card data, private keys or copyrighted customer content.