How to format to youtube shorts spec without premiere
- Step 1Know the spec you're targeting — YouTube Shorts: vertical 9:16, recommended 1080×1920, up to 60 seconds, H.264 in MP4/MOV, common frame rates (24/25/30/48/50/60 fps). The formatter handles all of these — you don't configure any of them.
- Step 2Rough-cut and frame your clip (in any tool, or none) — If your subject is centered and the clip is near-60s, you need no pre-step. If not, cut with lossless-trimmer or frame with video-cropper first — still no NLE required.
- Step 3Drop the clip onto the formatter — MP4, MOV, MKV, WebM, AVI, M4V, or TS — far more inputs than a typical NLE's quick-export presets. Loads into the in-browser FFmpeg.wasm filesystem, no upload.
- Step 4Run the spec pass — JAD probes the source, applies the centered 9:16 crop, scales to 1080×1920 (Lanczos), trims to 60s, and encodes H.264 CRF 20 + AAC 128 kbps with
+faststart— every spec requirement in one go. - Step 5Download the spec-compliant MP4 — The output is a 1080×1920 H.264/AAC MP4 that satisfies the Shorts spec with no manual checking. The source frame rate (one of the accepted Shorts rates in the vast majority of cases) is preserved.
- Step 6Upload to YouTube directly — Because the file already meets the spec, the Studio uploader or mobile app classifies it as a Short automatically (vertical + ≤60s). No re-export, no spec warnings.
YouTube Shorts spec → how the formatter meets it
Each Shorts requirement mapped to the exact pipeline stage that satisfies it. Nothing here is a manual setting.
| Spec requirement | Target | How the formatter meets it |
|---|---|---|
| Aspect ratio | 9:16 vertical | Centered crop to the 9:16 window |
| Resolution | 1080×1920 (recommended) | scale=1080:1920:flags=lanczos |
| Duration | ≤ 60 seconds | -t 60 (keeps first minute) |
| Video codec | H.264 | -c:v libx264 -preset medium -crf 20 |
| Pixel format | 8-bit 4:2:0 (universal) | -pix_fmt yuv420p |
| Audio codec | AAC | -c:a aac -b:a 128k |
| Container | MP4 (web-streamable) | MP4 with -movflags +faststart |
| Frame rate | 24/25/30/48/50/60 fps | Source fps preserved (no -r) |
Formatter vs. NLE / desktop encoders
Where the browser formatter wins and where a full editor is still the right call.
| Need | Formatter | Premiere / CapCut / HandBrake |
|---|---|---|
| Spec-perfect 9:16 export, fast | One click, no install | Manual sequence + export preset |
| Off-center / keyframed crop | No — pre-crop with video-cropper | Yes (manual) |
| Choose exact in/out range | No — pre-trim with lossless-trimmer | Yes (timeline) |
| Multi-clip edit / transitions | No — merge first with video-merger | Yes |
| Keep footage off any server | Yes — in-browser, no upload | Yes (local) but requires install |
| Burned captions | Separate pass: subtitle-burner | Yes (built in) |
Cookbook
The Shorts spec, demonstrated. Each example shows a requirement being met automatically — no preset to choose, no spec sheet to read.
The whole spec in one command-equivalent
What the formatter runs under the hood for a 16:9 source — every Shorts requirement is in this one FFmpeg invocation.
# Equivalent FFmpeg the browser runs (1920×1080 source): ffmpeg -i in.mp4 -t 60 \ -vf "crop=607:1080:656:0,scale=1080:1920:flags=lanczos" \ -c:v libx264 -preset medium -crf 20 -pix_fmt yuv420p \ -c:a aac -b:a 128k -movflags +faststart out.mp4 # 9:16 ✓ 1080×1920 ✓ ≤60s ✓ H.264 ✓ AAC ✓ faststart ✓
Wrong-codec source (VP9 WebM) → spec MP4
A screen-recorded WebM in VP9 isn't Shorts-friendly. The formatter decodes it and re-encodes to spec H.264/AAC MP4 — no codec setting needed.
Input: capture.webm 1920×1080 VP9 / Opus Formatter → decode VP9, crop+scale, encode H.264 + AAC Output: spec.mp4 1080×1920 H.264 / AAC (Shorts-compliant)
ProRes MOV master → upload-ready Short
A heavy ProRes export from an edit. No need to transcode in HandBrake first — the formatter takes the MOV directly and outputs the lightweight spec MP4.
Input: master.mov 3840×2160 ProRes 422 / PCM Formatter → crop 1216×2160, scale 1080×1920, H.264 CRF20, AAC Output: small spec MP4 (no separate HandBrake transcode)
Over-length clip auto-capped to spec
A 3-minute clip — the spec caps duration at 60s and the formatter enforces it without you setting an out-point.
Input: long.mp4 3:00 -t 60 → keeps 0:00–1:00 automatically Output: 60.0s 1080×1920 Short (spec duration ✓) (Pre-trim with lossless-trimmer if your moment is later.)
Odd phone resolution normalised to spec
A phone records 1080×2340 (not exactly 9:16). The formatter normalises it to the canonical 1080×1920 so uploaders treat it as a clean Short.
Input: phone.mp4 1080×2340 (taller than 9:16) Crop: center 9:16 window of the height Scale: → 1080×1920 (canonical Shorts size) Output: spec-perfect 1080×1920 MP4
Edge cases and what actually happens
You need a manual / off-center crop like in Premiere
By designThe formatter's crop is centered and fixed — there's no draggable crop box. Pre-frame with video-cropper (visual region picker) for the Premiere-style control, then run the formatter to hit the spec.
You need an exact in/out range like a timeline
By designThe spec pass keeps the first 60 seconds; there's no scrubber. Use lossless-trimmer for a precise range (it shows source duration and accepts start/end), then format.
Source frame rate isn't an accepted Shorts rate
PassthroughThe formatter preserves the source fps (no -r). The vast majority of footage is already 24/25/30/50/60. If you have an unusual rate (e.g. 23.976 is fine; something exotic like 15fps is unusual), convert fps with a dedicated tool first — this formatter doesn't change frame rate.
You expected the formatter to add captions like CapCut
By designCaptions aren't part of the spec pass. Burn them as a second pass with subtitle-burner, which has Shorts-style presets — keeping captions separate lets you re-style without re-encoding the crop.
You want transitions or multi-clip editing
Wrong toolThis is a spec formatter, not an editor — it takes one clip and outputs one spec MP4. For multi-clip work, assemble with video-merger first, then format the result.
Output file is larger than YouTube's old 256 MB hint
SupportedCRF 20 is high quality, so a 60-second 1080×1920 clip is typically well under any practical upload size. If you need it smaller for your own bandwidth, run web-optimizer on the result — but YouTube accepts large Shorts and re-encodes regardless.
Source is a non-MP4 container (MKV, AVI, TS, WebM)
SupportedThe formatter accepts more containers than most NLE quick-export presets and always outputs spec MP4 — so a MKV or TS capture is converted to Shorts spec in the same single pass, no separate remux.
10-bit / HDR source
Supported (tonemapped to SDR shape)Output is forced to 8-bit yuv420p for universal playback, so a 10-bit source is encoded to 8-bit SDR. Shorts and most phones expect SDR 8-bit, so this is the safe spec choice; colour may shift slightly versus an HDR master.
Probe can't read the source
ErrorIf dimensions can't be determined (corrupt header), the pass throws "Could not determine video dimensions." Re-export to a clean MP4/MOV from your editor, then format.
File exceeds your tier limit
RejectedFree 1 GB, Pro 10 GB, Pro-media/Developer 100 GB per file (no duration cap). A large ProRes/4K master may exceed Free — trim with the lossless trimmer or upgrade the tier to format it.
Frequently asked questions
Do I really not need Premiere or CapCut?
Correct — for hitting the Shorts spec (9:16, 1080×1920, ≤60s, H.264/AAC MP4) you don't. The formatter enforces every requirement in one browser pass with no install, no subscription, and no watermarked export.
What exactly is the YouTube Shorts spec?
Vertical 9:16 aspect, recommended 1080×1920, up to 60 seconds, H.264 video in an MP4/MOV container, AAC audio, and common frame rates (24/25/30/48/50/60). The formatter outputs H.264 MP4 at 1080×1920, ≤60s, AAC 128 kbps, with +faststart.
Is this as good as a HandBrake transcode?
It uses the same libx264 encoder HandBrake uses, at CRF 20 / medium preset, with +faststart — so the encode quality is comparable for Shorts. The difference is it's purpose-built: it also crops to 9:16 and trims to 60s in the same pass, which HandBrake doesn't do.
Can I control the crop or in/out like in an NLE?
Not in the formatter — the crop is centered and the trim is the first 60 seconds. For NLE-style control, use video-cropper (manual region) or lossless-trimmer (exact range) first, then format to spec.
What input formats can it take?
MP4, MOV, MKV, WebM, AVI, M4V, and TS — more than most NLE quick-export presets accept. Output is always spec MP4 (H.264/AAC, 1080×1920).
Does it handle ProRes or other heavy masters?
Yes — a ProRes MOV decodes fine and is re-encoded to the lightweight spec H.264 MP4, so you skip a separate HandBrake transcode. Large 4K ProRes files must fit your tier's size limit.
What about HDR or 10-bit footage?
Output is forced to 8-bit yuv420p SDR for universal playback — the safe Shorts choice. A 10-bit/HDR source is encoded to 8-bit, which may shift colour slightly versus the HDR master but ensures it plays everywhere.
Will it add captions or branding?
No — the spec pass outputs a clean MP4. Add captions with subtitle-burner and a logo with watermark-engine as separate passes afterwards.
Does my footage get uploaded?
No. The encode runs in your browser via FFmpeg.wasm — HandBrake-grade encoding, locally, with zero upload. Safe for unpublished or client work.
Why force 8-bit yuv420p — isn't that lower quality?
yuv420p (8-bit 4:2:0) is the universal-compatibility pixel format every device and browser can decode. It's the standard for web/Shorts delivery; higher chroma depth wouldn't survive YouTube's own re-encode anyway, so it's the right spec choice.
Can I edit multiple clips together first?
The formatter takes one clip. For multi-clip Shorts, join them with video-merger (concat for same-codec, transcode otherwise) and then run the merged file through the spec pass.
Will YouTube accept the file as a Short automatically?
Yes — because the output is vertical 9:16 and ≤60 seconds, YouTube classifies it as a Short on upload. You don't need a special export setting; meeting the spec is what triggers the classification.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.