PricingFill this in for one real project
| Measure | What to record | Why it matters |
|---|---|---|
| Source input | Number of files, minutes and storage size | More material may increase processing and selection work. |
| Initial output | Credits or charges actually used | Separate an estimate from completed processing. |
| Revision rounds | Each request and its actual charge | A usable result may require follow-up work. |
| Hands-on time | Preparation, review and finishing minutes | Automation still needs direction and judgement. |
| Accepted outputs | Only versions you would actually publish | Failed or unsuitable outputs do not count as deliverables. |
Calculate two useful numbers
Cash cost per accepted video = total processing and other project charges divided by the number of accepted videos. If you account for labour, add hands-on hours multiplied by your own hourly rate before dividing. Keep that rate explicit; it is your assumption, not a product benchmark.
Use Shorty’s current estimate
Check the live pricing page and the estimate shown in the product for your selected material. Google Drive folder preview shows the selected files and an estimate before you add them; checking or adding the folder does not itself use editing credits. Editing uses credits. Confirm the estimate again for the work you submit.
Compare the same finish line
A rough first cut and an approved client delivery are different outcomes. Include a realistic revision and the finishing you need. Note any frame-level work you move into another editor and any separate software cost.
Publish measurements with context
If you share a comparison, include the test date, source duration, brief, output requirements and what you counted as review time. Shorty has not published a measured speed or cost benchmark on this page.