# Video Converter API (`obedient_hierarchy/universal-video-converter`) Actor

Reliable FFmpeg-based Apify Actor that converts video and audio files between safe presets, validates input/output metadata, and stores converted files in the default key-value store.

- **URL**: https://apify.com/obedient_hierarchy/universal-video-converter.md
- **Developed by:** [Kritsana](https://apify.com/obedient_hierarchy) (community)
- **Categories:** AI, Developer tools, MCP servers
- **Stats:** 1 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Universal Video Converter API

Apify Actor for reliable FFmpeg-based video/audio conversion.

The actor accepts an uploaded file or direct URL from the Actor input UI, converts the file using a constrained preset, validates input and output with `ffprobe`, saves the converted file back to the default key-value store, and pushes a dataset item with metadata and a download URL.

### Example input

```json
{
  "sourceUrl": "https://example.com/input.mov",
  "targetFormat": "mp4",
  "quality": "balanced",
  "maxResolution": 1080,
  "fps": 30,
  "stripMetadata": true
}
```

### Console upload

In Apify Console, use the **Upload video or source URL** field. It renders as a file upload control, so non-technical users can upload a video directly instead of writing JSON or creating a key-value store manually.

### Upload workflow

For API clients, first upload the binary video to an Apify key-value store record, then run the Actor with a signed or token-authenticated record URL as `sourceUrl`.

```bash
curl -X PUT \
  "https://api.apify.com/v2/key-value-stores/YOUR_STORE_ID/records/input.mov?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: video/quicktime" \
  --data-binary "@input.mov"
```

```json
{
  "sourceUrl": "https://api.apify.com/v2/key-value-stores/YOUR_STORE_ID/records/input.mov?token=YOUR_APIFY_TOKEN",
  "targetFormat": "mp4",
  "quality": "balanced"
}
```

Use `sourceUrl` when the file is already hosted somewhere or uploaded to Apify storage. `sourceKey` is still supported for records available in the run's default key-value store. `sourceStoreId` is available for privileged runs, but public/signed `sourceUrl` is the most reliable upload workflow because Apify runs may execute with limited storage permissions.

### Supported formats

- Video: `mp4`, `webm`, `mov`, `mkv`, `avi`, `m4v`, `gif`.
- Audio: `mp3`, `m4a`, `aac`, `wav`, `ogg`, `flac`.

The actor does not accept raw FFmpeg command strings. This keeps the API stable and prevents command injection.

# Actor input Schema

## `sourceUrl` (type: `string`):

Upload a video/audio file or provide a direct URL. The Actor will convert this file using the selected output settings.

## `sourceKey` (type: `string`):

Alternative to sourceUrl. Key-value store record key containing the uploaded source file.

## `sourceStoreId` (type: `string`):

Optional Apify key-value store ID or name to read sourceKey from. Leave empty to use the run's default key-value store.

## `targetFormat` (type: `string`):

Output container/format. Presets are intentionally constrained for reliability.

## `quality` (type: `string`):

Controls encoder quality/speed. Higher quality creates larger files and slower runs.

## `maxResolution` (type: `string`):

Downscale video so neither side exceeds this size. Use 0 to keep original size.

## `fps` (type: `string`):

Optional output FPS cap for video formats. Use 0 to keep source frame rate.

## `startTime` (type: `string`):

Optional trim start, for example 00:01:10 or 70.5 seconds.

## `duration` (type: `string`):

Optional trim duration, for example 00:00:30 or 30.

## `stripMetadata` (type: `boolean`):

Remove embedded metadata from the output file.

## `outputKeyPrefix` (type: `string`):

Prefix for saved output keys in the default key-value store.

## Actor input object example

```json
{
  "targetFormat": "mp4",
  "quality": "balanced",
  "maxResolution": "1080",
  "fps": "0",
  "stripMetadata": true,
  "outputKeyPrefix": "converted"
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items with source metadata, output metadata, output key, output URL, and conversion settings.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "targetFormat": "mp4"
};

// Run the Actor and wait for it to finish
const run = await client.actor("obedient_hierarchy/universal-video-converter").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "targetFormat": "mp4" }

# Run the Actor and wait for it to finish
run = client.actor("obedient_hierarchy/universal-video-converter").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "targetFormat": "mp4"
}' |
apify call obedient_hierarchy/universal-video-converter --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,obedient_hierarchy/universal-video-converter"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3FdfNbMsjJHRIJdNs/builds/0vnPDh72bXSmNksm7/openapi.json