KinoPipe
Start for free

KinoPipe vs CloudConvert

CloudConvert turns one file format into another, across documents, images, audio, video and archives, and adds watermarks, thumbnails, merges and arbitrary commands on top. KinoPipe does one domain, video, and exposes it as bounded editing operations an agent can call. The question is whether your job is a format change or an edit.

Checked against public product pages on August 28, 2026.

Choose KinoPipe when
the job is an edit rather than a conversion: cut to timestamps found in a transcript, reframe to 9:16 by following the speaker, burn captions you generated, or rank the clip candidates in a long recording.
Choose CloudConvert when
the breadth of formats is the point: one account that also handles PDFs, spreadsheets, ebooks and archives, with roughly 200 formats behind a single API.
AreaKinoPipeCloudConvert
ScopeVideo and audio only, 43 typed operationsAround 200 formats across documents, images, audio, video and archives
Editing modelBounded operations with validated parameters; no shellConversion parameters per format pair, plus watermark, thumbnail, merge and an execute-command operation
Reading a videoTranscription with word timestamps, scene detection, per-scene description, ranked clip candidatesFile metadata
MCPRemote MCP with OAuth 2.1, tools create and poll jobsMCP server listed in the integrations documentation
Pricing unitCredits by worker seconds or 6 MiB of outputConversion credits: a base cost per conversion type plus roughly one credit per minute of conversion time
Free tierCredits on sign-up, no card10 conversions per day, 1 GB per file, 5 minutes of processing, 5 concurrent tasks
Test KinoPipe on your own source
Upload a file on any tool page, run a live job and download the result before choosing an API.
Run resize video Read API docs

Sources

CloudConvert pricingCloudConvert convert operation

Before you choose

Can CloudConvert do the video edits KinoPipe does?

Some of them. It converts, optimises, watermarks, creates thumbnails and merges, and it exposes an execute-command operation. What it does not publish is the reading side: transcripts with word timestamps, scene boundaries, per-scene descriptions and ranked clip candidates, which is what tells an agent which seconds to cut.

Which is cheaper?

It depends on the shape of the work rather than the rate. CloudConvert charges a base cost per conversion plus about a credit per minute of processing, so many short files cost more than one long one. KinoPipe charges by worker seconds or output size, so a batch of short clips is cheap and a long render is not.

Do I have to choose?

No, and for a mixed pipeline you probably should not. A document-heavy workflow that occasionally touches video is well served by one account at CloudConvert; a video workflow that needs to decide what to cut is not.