ForHosting KIT · Video

Video export preset lookup by platform

Get matching export settings for where the video is going: for YouTube the preset is H.264 at 3840x2160, 60 fps and 53 Mbps, with vertical formats for Instagram and TikTok and an HD preset for broadcast. Free in your browser.

Free
Runs in your browser
No sign-up
Your data stays on your device

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Worked example

If you enter

Platform: Youtube

You get

Codec: H.264
Resolution: 3840x2160
Framerate fps: 60
Bitrate mbps: 53

Choosing export settings should not require hunting through delivery notes every time a video changes destination. Each result includes the recommended codec, pixel resolution, frame rate in frames per second, and target bitrate in megabits per second. It is useful for configuring editing templates, validating automated renders, and giving production teams a consistent starting point.

Choose the destination before configuring the export

A technically excellent master can still be a poor delivery file when its dimensions, data rate, or frame cadence do not suit the place where viewers will receive it. Start by selecting the actual target platform rather than copying the settings from the editing timeline. YouTube is represented by a high-quality 4K delivery preset, while Instagram and TikTok use dimensions that match their common feed and vertical viewing formats.

The broadcast option uses a conventional high-bitrate HD preset intended as a practical handoff baseline. Send the platform as one of the four documented lowercase values and the lookup returns a complete, internally consistent recommendation. The response includes the platform again so logs remain understandable after a request is separated from its input.

It also gives numeric frame-rate and bitrate fields, making the result easy to compare, validate, or insert into another system without parsing display text. Treat the returned values as the delivery target, then preserve a higher-quality master separately for future versions and destinations.

Understand what every returned setting controls

The codec identifies the compression format expected for the delivery file. Resolution is returned as width by height in pixels, which communicates both image size and orientation: 1080x1920 is vertical, whereas 3840x2160 is landscape 4K. The frame-rate value describes how many distinct frames are encoded each second.

A higher number can preserve smoother motion, but it also creates more data and should not be invented when the source was captured at a lower cadence. Bitrate is the target video data rate in megabits per second and balances image detail against transfer size. More bitrate is not automatically better after a platform recompresses an upload, yet too little can introduce blocking, banding, and damaged motion before that second compression even begins.

These fields form one preset rather than independent maximums. Apply them together unless a documented delivery specification, broadcaster, client, or post-production supervisor gives you stricter requirements for the particular program. Audio settings are intentionally outside this capability so the response remains focused and unambiguous.

Use the preset as a repeatable production baseline

The lookup is most valuable when it removes small inconsistencies from repeated work. An asset-management service can request a preset when a destination is selected, pass the returned fields into an encoder configuration, and record the same result beside the rendered asset. A quality-control step can compare planned settings with the recommendation before a long render or upload begins.

Editors can also use the browser version as a quick reference when creating export templates in their preferred software. Because the algorithm contains a fixed table, uses no network service, and does not inspect the media, identical inputs always produce identical results. If a delivery contract provides exact technical rules, that contract takes priority.

Use this result as a sensible default when no more specific requirement exists, and run a visual quality check on the final encoded file.

What you can do with it

Configure an automated render

Translate a selected destination into stable encoder fields without maintaining another platform lookup in the rendering service.

Create editor export templates

Use the returned codec, dimensions, frame rate, and bitrate as the baseline for named presets in editing software.

Validate a delivery configuration

Compare planned settings with a consistent recommendation before spending time on a render, transfer, or upload.

FAQ

Which platforms are recognized?

The accepted values are youtube, instagram, tiktok, and broadcast. Any other value returns an invalid-input error.

Does the lookup inspect my video?

No. It returns a deterministic preset from the target platform and does not upload, decode, or analyze media.

Are these settings mandatory platform limits?

No. They are practical recommendations. A current client brief, broadcaster specification, or delivery contract takes priority.

Why are audio settings not included?

This capability has a narrow contract covering codec, resolution, video frame rate, and video bitrate only.

Can I use a different source frame rate?

Yes, but avoid creating frames merely to reach the preset. Preserve the source cadence when conversion would add no real motion detail.

Related tools

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/video2/export-preset-lookup

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/video2/export-preset-lookup \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platform":"youtube"}'

const res = await fetch("https://api.kit.forhosting.com/video2/export-preset-lookup", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "platform": "youtube"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/video2/export-preset-lookup",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "platform": "youtube"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/video2/export-preset-lookup", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"platform":"youtube"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"platform":"youtube"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/video2/export-preset-lookup", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "platform": "youtube"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "video2.export_preset_lookup",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

`max_mb`	500
`max_minutes`	60
`max_megapixels`	3.9

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Technical notes

This lookup returns one practical preset for YouTube, Instagram, TikTok, or broadcast in a predictable JSON object. The same deterministic lookup runs in the browser and through the API, where each request costs $0.002.

Technical questions

What does an API request cost?

Each API request costs $0.002. The browser version uses the same deterministic lookup.

Read the full KIT documentation →

Run — free