To sell Scrivener templates, export a reusable project template, remove private manuscript material, and give buyers an import route they can follow in their version of Scrivener. Deliver the template with a short guide in a ZIP. A finished PDF, an active project folder and a reusable template are different products.
This guide is for authors and writing coaches selling their own planning systems. The release card below connects a clean template export to PayRequest's actual file-delivery workflow. It is a protocol for you to run, not a claim that we tested your template or that every Scrivener version behaves identically.
Define What Your Scrivener Template Includes
Start with one writing job: planning a series, organizing interview research or outlining a branching story. Describe the structure the buyer receives and show it with your own demonstration content. Avoid promising that a folder structure will write the book or guarantee publication.
Specify the supported Scrivener version and operating system. If you have checked both macOS and Windows, record both; otherwise name the tested environment and leave other combinations unverified. A buyer also needs their own suitable Scrivener license. Your download does not include the application.
A Notion template normally uses a different distribution model. A finished EPUB ebook serves readers rather than writers creating new projects. Make that distinction clear before checkout so a buyer does not purchase a planning tool while expecting a book.
Export the Template, Not Just the Manuscript
Literature & Latte's customization export guide explains how to save a project as a template, then export that template from the new-project template screen. The resulting extension is .scrivtemplate. A separate compile-format export uses .scrformat; do not treat those files as interchangeable.
| Artifact | Buyer expectation | Seller check |
|---|---|---|
| .scrivtemplate | Create a new project from a reusable structure | Import it and create a fresh project |
| .scrformat | Apply a specific compile format | Document its separate import route |
| PDF guide | Read setup and usage instructions | Label it as documentation |
| Retail ZIP | Carry the template and supporting documents | Extract it before importing the intended file |
Use a release copy rather than your only working manuscript. In that copy, prepare the structure, save it as a template and export the template. The exact menu wording can vary by platform; use the instructions matching the version you advertise. The official Windows manual covers project templates and their import/export options.
Do not package a random internal project file because its name looks similar. The acceptance test is whether the delivered artifact creates the promised new project through the template workflow, not whether something opens on your own computer.
Remove Private Material Before You Create the Release
Inspect everything a buyer could receive: draft chapters, research documents, notes, comments, snapshots, contact details, imported media and discarded material. Remove anything you do not intend to distribute from the release copy. Keep the original safely separate. A blank main editor is not proof that the whole project is clean.
Replace personal examples with original demonstration text. Open every section of a fresh project created from the exported template and search for names, email addresses and other known private terms. Check linked resources too. A reference that works because it points into your personal folders may fail for the buyer.
Review redistribution rights for images, questionnaires, worksheets and framework descriptions. Buying a writing course does not itself grant permission to resell its worksheets. Describe your own approach and include only material you can distribute. A license should explain what the purchaser may do with your template and whether sharing the source file is permitted.
Use a Buyer Import Release Card
Create a small record for every version you sell. The following example is an original acceptance checklist, not a completed product test. Record actual results before advertising compatibility.
| Check | Evidence to retain | Failure action |
|---|---|---|
| Release identity | ZIP name, release date and template filename | Correct mismatched files |
| Clean export | Private-content review of a newly created project | Rebuild from the clean copy |
| Buyer import | OS, Scrivener version and exact import steps | Fix instructions or narrow support |
| Promised structure | All included folders, sheets and examples present | Repair missing content |
| Independent opening | Fresh project works without seller-only resources | Bundle permitted resources or disclose dependency |
| Paid delivery | Downloaded archive matches the approved release | Correct the uploaded artifact |
For example, Series-Planner-v1.zip might contain Series-Planner.scrivtemplate, Start-Here.pdf and License.pdf. The guide should name the exact template file, explain how to extract the ZIP and show the tested import route. Then have the buyer create a new project from that template. Do not tell them to import the ZIP itself as a template.
If your promise includes formatted output, test that separately with a sample project. Successfully importing a planning template does not prove that its PDF or EPUB output meets a publisher's specifications. State what you actually checked.
Deliver the Approved Scrivener Template With PayRequest
Create the offer through PayRequest digital products and upload the approved ZIP. The current upload allowlist, reviewed on 11 September 2026, accepts ZIP but does not list .scrivtemplate or .scrformat as direct uploads. Packaging them in a ZIP gives the buyer one supported delivery artifact without claiming native extension support.
Review the expiry and download allowance in file delivery. In the current download implementation, visiting the landing page and performing a download are separate actions. Neither proves that Scrivener imported the file successfully. For support, ask which stage failed: payment, access, archive extraction, template import or new-project creation.
Keep the release card and compatibility records in your own documentation. PayRequest delivers the file; it does not inspect private manuscript content or run Scrivener. Protected download access also does not prevent a purchaser from copying an already downloaded archive.
Before launch, state whether future updates are included and how buyers will receive them. Keep versioned copies so a support request can be matched to the artifact sold. Check current pricing when setting your offer: the Free plan charges 2% per successful payment, capped at €25 per transaction, with payment-provider fees separate. Start with one verified template and create its digital-product offer.
Editorial note: AI assisted with this article and illustrative cover. PayRequest upload and download behavior was reviewed in code. The release card and example package are original planning tools; no customer results or completed Scrivener tests are claimed.