To sell SRT subtitle files online, package the exact timed-text files, disclose language and compatibility, test the timecodes and deliver the archive only after payment is confirmed. An SRT is a small file, but buyers still need to know what video version it matches and whether they receive translation, editing or commercial-use rights.
This guide is for subtitle editors, accessibility specialists, course creators and video teams selling original subtitle packs. Its original asset is a release matrix for filename, language, timecode check, encoding, licence and delivery. It is a product-release workflow, not a claim that any subtitle file has been tested here.
Decide what the buyer is purchasing
Name the source-video version, language or locale, subtitle type, included revisions and permitted use. Keep a separate offer for transcription, translation, timing repair and a finished video with burned-in captions. A buyer should not infer that buying an SRT includes the underlying video, translation rights or editing support.
| Release field | Example record | Why it matters |
|---|---|---|
| File identity | lesson-04.en-US.srt | Prevents a language/version mismatch |
| Timing basis | 23.976 fps source, 18:42 duration | Lets the buyer compare the source |
| Text scope | English captions with speaker labels | Defines what is included |
| Licence | One buyer project, no raw-file resale | Avoids an accidental rights promise |
The example values are a release format, not a standard. Match the actual source and the rights you own.
Test an SRT before selling it
Open the file in a subtitle editor or video player that supports SRT. Check that numbering is sequential, each time range is valid, captions do not overlap unexpectedly and the final cue does not extend beyond the source. Review long lines, speaker labels, music descriptions and characters such as accents or apostrophes.
Rename the retail file consistently and open the exact ZIP from a different folder. Include a short read-me with the source version, import steps, encoding, licence and support route. Do not include the private video, client footage or an unfinished working file unless the offer says so and you have permission.
Build a buyer-safe download package
For one subtitle file, a direct SRT download may be enough if your delivery flow accepts that format. For a pack, use a ZIP with a manifest and separate language folders. Keep preview screenshots or a short sample outside the paid file unless they are licensed and clearly labelled.
PayRequest digital products and file delivery provide the hosted sales and download path. Confirm the current file allowlist, size limits and download behavior in your account before promising a format. PayRequest does not validate timecodes, translation quality, copyright or software compatibility.
Connect payment to the correct release
Create one product for one clear subtitle release or pack. Put language, source version, file count and licence in the product description. Test the public page, payment confirmation and download in a private window. Deliver the file after the configured successful payment state, not after a screenshot or an abandoned checkout.
Track product version, file hash or manifest name, buyer order, payment reference and delivery event. If you fix timing, publish a new version and state whether previous buyers receive the update. Never overwrite a buyer's expected file silently when the licence or contents changed.
Choose the right PayRequest destination
Use PayRequest digital products when the buyer should receive an SRT or ZIP automatically. Use a payment link when the offer is simple but still needs a hosted checkout. If the work is custom captioning, use invoicing to collect the approved service and deliver according to your service agreement.
Review pricing before setting your margin: the Free plan has no monthly charge and PayRequest charges 2% per successful payment, capped at €25 per transaction, with provider fees separate. Publish only after the exact retail archive opens and imports as the listing promises.
Editorial note: AI assisted with this article and its illustrative cover. The release matrix and test sequence are original planning tools; no SRT, player, translation, customer result or compatibility outcome was tested for this article.
