To sell DaVinci Resolve templates and macros online, package the installable files, a short setup guide and the required assets into a versioned ZIP. Show the editable controls, tested Resolve edition and dependencies before checkout, then deliver that exact package after payment. A beautiful preview is useful only if the buyer can reproduce the result.
This guide is for motion designers selling titles, transitions, generators or reusable Fusion effects. For color-grading products, use the separate PowerGrade selling guide.
Choose one editing task your product completes
Start with a narrow offer such as lower thirds for interview editors. Describe what the editor can change: names, colors, duration, position and any logo placeholder. A bundle called “100 professional effects” tells the buyer less than a smaller pack with clear controls and an honest demonstration.
Blackmagic Design explains how Fusion templates expose selected controls on the Edit page. That provides a useful product promise: show the controls you actually expose. Do not advertise every internal node as a convenient buyer setting.
Build a delivery package a stranger can use
The following is an original packaging example, not a tested Resolve product or a required folder standard. Adapt the installer and extensions to your actual export.
| Package item | What to put there | Buyer question answered |
|---|---|---|
| install/ | Your installable template or macro files | What do I install? |
| start-here.pdf | Installation, where it appears, removal and support | How do I get started? |
| assets/ | Only assets you may redistribute | What else is required? |
| examples/ | An optional lightweight example using included assets | What should the result look like? |
| compatibility.txt | Exact tested versions, editions and platforms | Will it work in my setup? |
| terms-and-changelog.txt | Usage terms, release date and changes | What did I buy? |
If you use a DRFX installer, place it inside the delivery ZIP with the guide. Do not rename another file to DRFX. PayRequest's general digital-download flow accepts ZIP; confirm the current upload limit in the digital-product documentation before preparing a large pack.
Copy this compatibility and acceptance checklist
Download the editable release checklist. Complete one record per advertised configuration. Blank fields mean untested, not compatible.
- Record the package filename, release identifier and checksum.
- Record Resolve version, Free or Studio edition, operating system and required plugins or fonts.
- Install the retail package in a clean profile or separate test environment.
- Locate the template and change every advertised control.
- Try short and long titles, another clip duration and the promised aspect ratios.
- Render a representative timeline; check missing media, font substitution and visible artifacts.
- Remove the package and follow your own reinstall instructions.
Publish only the configurations you have actually checked. If a required effect needs Studio or a separate paid plugin, state that next to the purchase action. A version number in a filename does not prove compatibility.
Write a sales page around the buyer's workflow
Include a screen recording of the retail files, an inventory of templates, approximate download size and the support contact. Show at least one customization rather than only a finished montage. If demo footage, fonts or music are excluded, say so before payment.
State the usage rights for the assets you created and review third-party redistribution rights. Paying for a font, stock clip or plugin does not by itself establish permission to include its files in your download. Offer personal or team editions only when you can explain the different permissions clearly.
Deliver the ZIP after confirmed payment
Create a DaVinci Resolve template product, upload the approved ZIP and connect a supported checkout provider. Set a price and the download-access terms, then check the customer-facing description. Run a buyer-view purchase and installation before promoting the offer; this article does not claim that such a purchase has been performed for your files.
Use digital file delivery for the handoff. Do not send buyers a public master folder or treat a checkout screenshot as confirmation that money arrived. Keep a separate release archive so support can identify what changed.
File delivery is different from an in-app updater or license server. If you promise automatic update notifications, activation limits or a paid support term, verify and operate those separately. A replacement file should preserve the installation guide and terms, not just the latest binary.
Plan a price without promising a marketplace income
Assume an illustrative €25 pack and twenty standard sales on PayRequest Free: €500 in sales and €10 in standard platform fees before provider fees, tax, refunds and other costs. This is arithmetic, not a forecast or a recommended market price. Free charges 2%, capped at €25 per transaction. Premium (€5/month) and Business (€20/month) remove standard platform fees while paid access is active; provider fees and commission exceptions remain separate. Check current plans against the features and selling period you need.
Start with one pack that solves a clear editing task. Publish the compatibility record alongside a useful preview, then share the product page with the audience that already watches your editing tutorials.
Editorial method: prepared with AI assistance, an original release checklist and official product documentation reviewed on 8 November 2026. Package names, prices and sales counts are illustrative. No installation test, customer result or sales forecast is claimed. The cover is an AI-generated conceptual illustration.
