WebCodecs in this tab
The browser demuxes, decodes, and re-encodes on this device with WebCodecs. The file stays in this tab.
Kling Motion Control · Reference video · No upload
Prepare a reference video
for Kling Motion Control.
How do I prepare a reference video for Kling Motion Control?
Trim the clip to 3–30 seconds, keep it to one continuous shot with the head and body in frame, and keep the frame between 340 px (short edge) and 3850 px (long edge), per Kling's guide. This page trims and compresses in your browser, no upload. Kling's guide and fal's page give no file format or size limit.
Kling AI: Motion Control user guide; fal: Kling v3 standard Motion Control API
Last updated
Set a start and end so the clip runs 3–30 seconds, then compress it on this device. Frame size is checked against Kling's published 340 px and 3850 px range.
100% Local
No Upload
Your video never leaves this device
Privacy clean output
What Kling publishes about the reference video
Checked on 2026-10-19 against Kling's Motion Control guide and fal's Kling v3 motion control page. The guide's requirements list sits under its VIDEO 2.6 Motion Control section; the VIDEO 3.0 section of the same page does not give a separate list. Limits can change, so confirm on the source before a long job.
| Item | What the source says | Source |
|---|---|---|
| Duration | 3–30 seconds for an uploaded action video. The generated video is as long as the upload. | Kling guide, requirements list |
| Frame size | Short edge at least 340 px, long edge at most 3850 px. | Kling guide, requirements list |
| Shot | One continuous shot with the character in frame. Avoid cuts, shot changes and camera movement, or the video may be truncated. | Kling guide, requirements list |
| Subject | Entire body and head clearly visible and not obstructed. One character; with two or more, the one taking the largest part of the frame is used. | Kling guide, requirements list |
| Speed | Avoid overly fast motion; steady, moderate movement works best. | Kling guide, requirements list |
| Maximum length by orientation | character_orientation "video": up to 30 s. "image": up to 10 s. | fal model page, Input |
Not listed: a file format and a maximum file size. Neither page states one for the reference video, so this page does not either.
Trim and compress in four steps
- Drop the video on the box above. Its length and frame size appear in the file details.
- Type a start and an end in seconds or minutes:seconds. Pick a stretch that stays inside one shot and keeps the head and body in frame.
- Read the line under the trim fields. It says whether the clip length is inside 3–30 seconds and whether the frame size is inside 340 px and 3850 px.
- Press Compress locally and save the file. Upload that file to Kling or to the API service you use.
The compressor re-encodes the clip, so the saved file is a new copy. Related: Video Compressor, Video Upscaler, Video Metadata Viewer to read a clip's length and frame size, and video size limits by platform.
▶
Drop an MP4, MOV, or WebM
MKV is accepted when the browser can decode it. Processing stays in this tab.
No preview
Video
— · source stays on this device
Destination target:
Detecting…
Load a video to check its length and frame size.
Compressing0%
- Elapsed
- 00:00
- Remaining
- —
- Processing FPS
- —
- Source duration
- —
- Bytes written
- —
- Ratio so far
- —
- Path
- —
- Target resolution
- —
Compressed locally
- Original
- —
- Compressed
- —
- Saved
- —
- Time
- —
- Speed
- —
- Codec
- —
- Engine
- —
- Resolution
- —
Privacy clean output
Saved directly to the file you chose.
Verify it yourself (F12 Network)
This workflow processes your file in this browser tab. Opening DevTools is optional; it is the simplest way to watch what the page actually requests.
- Press F12 (or ⌥⌘I). Open DevTools, then the Network tab, before you start.
- Start the local job (clean, OCR, compress, merge).
- You can also disconnect the network after the page has loaded its UI. Same-origin engine/WASM/language files may still be cached from an earlier visit.
- Your file bytes are not POSTed to CreatorPrivacyKit for this step. Page HTML, CSS, and same-origin runtime assets still load over the network when they are not cached.
Expected Network activity: this site’s CSS/JS, and — after you run the tool — same-origin WASM, codec, or OCR language data. That is a download of our engine, not an upload of your file.
- Processing location
- This browser tab
- Media upload to our servers
- Not part of this workflow
- Remote analysis of your file
- No
This panel is a product fact, not a live packet sniffer. We do not invent a request counter. Ads, extensions, and your own later clicks can still create network traffic.
How compression runs in this browser, with no upload and no server queue
Decode, scale, and encode happen in this tab. CreatorPrivacyKit does not take the video for a server transcode.
No upload to this site
Frames and audio stay in this tab’s memory and temporary browser storage. There is no compressor upload API. That is a real difference from a converter that needs the whole file first.
Watch the Network panel
Open Developer Tools, switch to Network, and start a compress. The media file is not posted to a CreatorPrivacyKit transcode endpoint. Disconnecting the network is a rough extra check, not a formal audit.
Compare the exported bytes
Compare the download with the input. The page shows the byte change. A megabyte target is the upper size you set.
Local browser versus a cloud converter
Upload converters need the whole file first. This page compresses on this device. That is the upload difference. It is not a claim that nothing can go wrong on this computer.
| What you are comparing | This page (browser, no upload) | Typical upload converter |
|---|---|---|
| File upload | No upload The source stays in this browser. | Full upload The whole file is sent to a remote host. |
| Queue | Starts on this machine. There is no shared transcode line. | Often queued. Free tiers delay or cap jobs. |
| Size plans | No paid file-size plan. You are still limited by this device. | Free tiers often cap megabytes and charge for more. |
| Where the file sits | We do not keep a copy of your video on our servers. | Files commonly sit on the converter’s disks for a while. |
| What still can go wrong | No upload to this site. Malware on this device, a browser bug, or you later uploading the output are still possible. | A server breach, staff access, or a misconfigured bucket can expose the original. |
| Container metadata | Re-encoding writes a new MP4 (H.264) or WebM (VP9/AV1) and drops supported container metadata. Pixel-domain watermarks stay. | Behavior varies. Some keep camera headers or add converter tags. |
Size targets for Discord, email, and chat apps
These figures come from vendor help pages checked in September 2026. Apps change limits. A preset is a target — look at the file you actually get.
Discord
20 MB non-Nitro (FAQ, Aug 2026) · 50 MB Nitro Basic · 1 GB NitroDiscord’s File Attachments FAQ lists 20 MB for non-Nitro chat attachments as of August 2026, with 50 MB on Nitro Basic and 1 GB on Nitro. Discord also says it is testing other caps for some users, so the number in your app wins. The in-tool 19 MB Discord target is a margin under the stated 20 MB, not a send guarantee. Nitro was 500 MB. Server Boost Level 2 is 50 MB and Level 3 is 100 MB, for members of that boosted server only. Discord checks file size before its own compression, including on mobile. Open the Discord compressor or read the 20 MB field note.
Source updated August 2026 · checked September 21, 2026 Official source
Email attachments
Gmail consumer ~25 MB then Drive · Outlook.com and internet accounts 20 MB message size · Exchange default 10 MBGmail Help says consumer accounts typically allow about 25 MB of attachments and then insert a Drive link. Workspace attachment size is set by the administrator. Outlook on Outlook.com and internet accounts uses a 20 MB message size, which includes the attachment and the message. The Exchange default is 10 MB, and an administrator can change it. MIME/Base64 can make the sent size larger than the file on disk. Compress for Gmail or Outlook or read the email attachment note.
Checked September 21, 2026 Official source
WhatsApp Help puts a 64 MB ceiling on videos sent as video. Faster connections may default to 100 MB / 720p. Sending as a document is a separate 2 GB path. Those are upload caps, not a promise WhatsApp will keep your bitrate.
Checked September 21, 2026 Official source
LINE
Chat has no official MB cap · VOOM ended 30 Sep 2026LINE chat still has no official universal video MB cap. LINE VOOM, including Official Account VOOM posts, ended 30 September 2026 (around 11:00 JST) per LINE Help. Account rollout varies, and some Official Account content remains in LINE Home. Historic VOOM posts were 500 MB; that was not a chat limit. Official Account broadcast video is still 200 MB. Chat and broadcast messaging continue. Check the size LINE shows before you send.
Source updated July 2026 · checked September 30, 2026 Official source
Telegram
2 GB free · 4 GB Telegram PremiumTelegram’s FAQ lists 2 GB per file on a free account and 4 GB on Premium. Send-as-file can keep container metadata such as GPS. See the send-as-file metadata note.
Checked October 14, 2026 Official source
Local creator workflows
No upload here — still limited by this deviceFor client reviews and unreleased footage, keep the camera master offline and make a smaller MP4 on this device. Video compression guide · Compress without uploading.
Kling reference video questions
Kling's guide lists a duration of 3 to 30 seconds, a short edge of at least 340 px and a long edge of at most 3850 px, one continuous shot with no cuts or camera movement, and a clearly visible head and body. The table on this page shows each limit with its source.
Not on the two pages this page relies on. Kling's motion control guide and fal's model page do not state a format or a size limit for the reference video, so this page does not give one. Check the upload screen or API reference of the service you use.
Kling's guide gives 3–30 seconds for uploaded action videos. fal's page adds that the limit depends on character_orientation: 30 seconds for "video", 10 seconds for "image". If you use image orientation, set the end of the clip 10 seconds after the start.
Not to CreatorPrivacyKit. The clip is decoded and re-encoded by this browser tab. You upload the finished file to Kling or fal yourself.
It checks two things it can measure: the clip length against 3–30 seconds and the frame size against 340 px and 3850 px. It cannot see cuts, camera movement, whether the whole body is in frame, or how fast the motion is.
Kling says the action video should be a single continuous shot and that cuts can lead to truncation. Pick a start and end inside one shot, then trim.
Yes. Kling says that with complex or very fast motion the model keeps only the valid continuous part of the action, and that it needs at least 3 seconds of usable motion. It also says credits used in that case are not refunded.
The compressor only scales down. The Video Upscaler can enlarge frames by resampling, which makes the picture larger but does not add detail.
Audio is kept unless you clear Keep audio in the advanced controls. On fal's page, keep_original_sound is a separate input and defaults to true.