Cross-Platform Product Video Export Checklist
Export and verify product videos for YouTube, Shorts, LinkedIn, and Instagram Reels with practical checks for aspect ratio, codecs, captions, file identity, and playback.
A product video that looks polished in an editor can still fail after upload. A vertical crop can cut off the product, a platform can recompress fine text into a blur, captions can sit under interface controls, or an old offer can remain live after a campaign ends. The safest workflow is not “export once and upload everywhere.” It is to preserve one approved master, create controlled delivery versions, and verify what each platform actually published.
This checklist is for ecommerce marketers, creative teams, agencies, and founders preparing short product videos for YouTube, YouTube Shorts, LinkedIn, and Instagram Reels. It focuses on decisions a team can verify: aspect ratio, codec, frame rate, audio, captions, crop safety, file identity, publication status, and post-upload playback. Platform limits change, so confirm the linked official specifications before a high-value campaign.
Quick answer: what should a cross-platform export pack contain?
Keep one high-quality approved master and derive at least two delivery layouts when the campaign needs both conventional and short-form distribution: a 16:9 landscape version and a 9:16 vertical version. Add a square or 4:5 version only when a destination or placement genuinely needs it. Do not stretch one canvas into another. Reframe the product, demonstration, captions, and call to action for each layout.
For every delivery file, record the destination, dimensions, frame rate, duration, codec, audio state, caption method, offer version, checksum or stable file name, approver, and upload result. After upload, watch the published result on a phone and desktop where relevant. The uploaded file is not the final evidence; the published playback is.
1. Separate the approved master from delivery variants
The approved master is the highest-quality version that represents the final creative decision. It should not be overwritten each time a platform version is produced. Lock its product appearance, approved claims, offer language, timing, music rights, spoken copy, caption text, and end card. If any of those elements change, create a new master revision and route it through review again.
Delivery variants are controlled derivatives. A variant may change canvas size, crop, caption placement, end-card duration, or compression settings, but it should not silently change the underlying claim or product demonstration. This distinction prevents a common review failure: the legal or merchandising team approves one video while a different, lightly edited version is actually published.
- Master: the approved source of truth for content and product representation.
- Layout variant: a deliberate 16:9, 9:16, square, or 4:5 composition.
- Delivery file: the encoded file submitted to a specific destination.
- Published result: the platform-hosted video viewers can actually watch.
2. Build a destination map before exporting
Do not begin with a generic list of social networks. Begin with the real placements in the campaign. “YouTube” can mean a conventional watch-page video or a vertical Short. “LinkedIn” may mean an organic feed upload or an advertising workflow with different requirements. “Instagram” may mean a Reel published through the app or a server-side publishing integration. The destination map turns vague distribution into testable outputs.
| Destination | Typical layout decision | Primary review risk | Required evidence |
|---|---|---|---|
| YouTube watch page | Usually 16:9; preserve the native composition | Soft text, resampled motion, weak thumbnail or opening | Processing complete; HD playback checked |
| YouTube Shorts | Usually 9:16 with vertical reframing | Captions or product details under interface areas | Mobile playback and crop checked |
| LinkedIn feed | Landscape, square, or vertical according to the post plan | Small product detail and muted-first viewing | Feed preview, captions, and post identity checked |
| Instagram Reels | 9:16 recommended for the vertical experience | Unsafe top/bottom text, cover crop, audio mismatch | Published Reel, cover, audio, and caption checked |
When a destination is not confirmed, do not create speculative variants “just in case.” Every extra export adds approval, storage, naming, and publishing risk. Produce only the files the campaign has an owner and destination for.
3. Protect source quality before compression
Compression cannot restore detail that was already lost in the source. Before exporting, review the product edges, labels, texture, small controls, reflected highlights, hands interacting with the product, and any motion that reveals shape. AI-generated clips need an additional continuity pass because a product can drift between frames even when a single frame looks convincing.
Use the AI product video review checklist to catch identity, motion, and claim problems before delivery work begins. If viewers cannot reliably recognize the same product from start to finish, platform settings are not the next problem to solve.
- Confirm the source resolution is sufficient for the largest required crop.
- Check that the source frame rate is known and consistent.
- Remove accidental letterboxing or pillarboxing from the master.
- Keep text and graphics as editable layers until each layout is approved.
- Retain clean dialogue, music, and effects stems when audio may need revision.
4. Prepare the YouTube landscape export
YouTube’s current official guidance recommends an MP4 container with H.264 video, progressive scan, and the same frame rate used for recording. It lists common frame rates such as 24, 25, 30, 48, 50, and 60 frames per second, and recommends AAC-LC or other supported audio at 48 kHz. The guidance also provides reference upload bitrates by resolution rather than imposing one universal bitrate.
For a conventional product walkthrough, 1920×1080 is a practical 16:9 delivery size when the source supports it. Avoid upscaling a weak source merely to produce a larger number. Encode at the source frame rate, inspect fast product motion and fine label text, and place the MP4 metadata for fast start when your encoder exposes that option.
YouTube adapts its player to other aspect ratios, so a vertical or square upload is technically possible. That does not mean one composition is equally effective everywhere. Use the aspect ratio that serves the intended viewing experience, and keep the product large enough to understand without forcing a viewer to zoom.
Official reference: YouTube recommended upload encoding settings.
5. Reframe intentionally for YouTube Shorts
A vertical Short should be a designed version, not a center crop generated at the final minute. Review every shot for the product’s position, hand movement, demonstration area, captions, price or offer text, and end card. If a wide shot contains two important objects, decide which one leads in the vertical version or redesign the sequence.
Keep essential text away from the extreme edges and from areas commonly occupied by playback controls. Interface layouts can evolve, so do not rely on one permanent pixel template. Use conservative margins, preview the final upload on an actual phone, and treat the platform-hosted result as authoritative.
When the same campaign uses both landscape and vertical versions, give each a distinct file identity. A filename such as product-launch-r03-yt-16x9.mp4 is safer than final-final2.mp4. Record which master revision produced it.
6. Prepare the LinkedIn feed version
LinkedIn’s current Help documentation lists a broad organic video range: file sizes from 75 KB to 5 GB, durations from three seconds on desktop up to 15 minutes, resolutions from 256×144 to 4096×2304, aspect ratios from 1:2.4 through 2.4:1, frame rates from 10 to 60 fps, and bitrates from 192 Kbps to 30 Mbps. These are acceptance boundaries, not a recommendation to use the smallest possible file.
Choose the layout based on the feed experience and the content. A square or vertical composition can give a product more screen area in a mobile feed, while landscape can suit a side-by-side demonstration. In every case, assume some viewers begin with limited or muted audio. The opening should establish the product and task visually, while captions carry spoken meaning.
LinkedIn’s marketing Videos API documentation can describe different limits for API-based workflows than the general member-upload Help page. Record whether the team is using an organic interface, an advertising workflow, or an API integration, and validate against that exact path instead of combining limits from different products.
Official references: LinkedIn organic video requirements and LinkedIn Videos API.
7. Prepare the Instagram Reels version
Meta’s published Reels API collection currently documents MOV or MP4, AAC audio at 48 kHz, HEVC or H.264 video, 23–60 fps, a recommended 9:16 aspect ratio, no more than 1920 horizontal pixels, a maximum video bitrate of 25 Mbps, and duration and file-size boundaries for server-side publishing. These specifications describe that publishing interface; app behavior and advertising placements can have additional rules.
Use a true vertical composition when Reels is a primary destination. Check the product silhouette, interaction area, captions, offer, and call to action at phone size. Review the selected cover independently because a good motion frame may crop poorly in a profile grid or preview surface.
If a server-side publishing workflow uses a temporary media URL, record when it expires and confirm the platform fetched the file successfully before removing the source. A request accepted for processing is not necessarily a published Reel. Preserve the media container ID, final post identity, and verification time where the integration exposes them.
Official reference: Meta Instagram Reels publishing collection.
8. Treat captions and audio as delivery components
Captions are not decoration. Compare the final caption text with the approved spoken copy, verify timing after the last edit, and make sure product names and technical terms are correct. Decide whether captions are burned into the video, uploaded as a separate track, or generated and corrected inside the platform. Record the choice for each destination.
Burned-in captions offer visual consistency but cannot be turned off and can be damaged by a different crop. Separate caption tracks can improve accessibility and viewer control but require accurate file preparation and platform support. Platform-generated captions still need human correction. A useful export pack can include a reviewed transcript even when the destination handles captions separately.
Follow the complete accessible product video checklist for captions, meaningful audio, transcripts, audio description, and motion review. That process should happen before the delivery files are approved, not after complaints arrive.
9. Run a crop-safety review for every layout
Overlay the intended crop guides in the editor and watch the complete video, not just the opening frame. Product motion can cross an unsafe boundary later. Check hands, packaging, labels, comparison objects, subtitles, discount text, disclaimers, logos, and calls to action. Give special attention to shots with pans, zooms, simulated camera motion, or 3D breakout effects.
Do not solve a crop problem by shrinking everything until the product feels distant. Recompose the shot. Move the product, shorten text, split a comparison across scenes, or create a destination-specific end card. The goal is not merely to keep every pixel visible; it is to preserve the intended information hierarchy.
10. Inspect the encoded file before upload
Open the exact delivery file outside the editor. Watch from start to finish with sound on, then again muted. Scrub through high-motion sections and pause on fine product details. Confirm that the duration, dimensions, frame rate, audio channels, and file size match the delivery record. If the team has a media-inspection tool, save its technical readout with the approval evidence.
- No unexpected black bars, stretching, or rotation.
- No clipped first or last spoken word.
- No missing music, effects, or dialogue channel.
- No caption collision with the product or end card.
- No visible banding, blockiness, or unreadable small text.
- No stale price, date, availability, or promotional condition.
- No metadata or filename that exposes private client information.
11. Give every approved file a stable identity
A good naming convention makes the destination and revision clear without opening the file. Use a pattern your team can maintain, such as campaign-product-revision-destination-layout-language.ext. Keep the approved file in controlled storage and calculate a checksum when exact identity matters. If the uploader or automation reports a timeout, the checksum and file record help determine whether a retry would duplicate the same asset or submit a different revision.
The delivery manifest should connect the file to its master, approver, platform, post or upload identity, and public URL. Do not place secrets, signed URLs, access tokens, or private customer data in that manifest.
12. Distinguish uploaded, processing, published, and verified
These states are not interchangeable. An upload can finish while processing later fails. A publishing request can return an identifier while the post remains unavailable. A timeout can occur after a platform accepted the file. Retrying without reconciliation can create duplicates.
- Uploaded: the destination received the file or returned an upload identity.
- Processing: the platform is transcoding or validating the media.
- Published: a platform record exists in a public or scheduled state.
- Verified: the intended public or scheduled result was opened and checked.
After an uncertain response, search for the expected post, media identity, scheduled item, or destination URL before retrying. Keep retries bounded. If the platform state cannot be established, stop and mark the operation uncertain rather than changing the file name to force a second submission.
13. Verify the platform-hosted result
Watch the published video because platforms transcode, crop, normalize, and present media differently. On mobile, confirm the product remains visible behind interface controls, captions are readable, the cover frame works, audio is synchronized, and links or calls to action point to the intended destination. On desktop, check the conventional watch or feed surface where relevant.
Record the public URL, publication time, account, final duration, visible offer, and reviewer. For a scheduled post, verify both the schedule and the result after its publication time. For an expiring campaign, assign an owner to remove or revise outdated creative according to the business policy.
14. Compact cross-platform export checklist
- Approved master revision is locked and identifiable.
- Every destination and publishing path is named.
- Each layout is deliberately reframed rather than stretched.
- Product identity and motion passed final QA.
- Claims, prices, dates, and offers match the approval record.
- Codec, container, dimensions, frame rate, and audio were inspected.
- Captions and transcript were reviewed after the final edit.
- Text and product action stay inside conservative crop-safe areas.
- Every delivery file has a stable name and destination record.
- The exact encoded file was watched before upload.
- Uncertain uploads are reconciled before retrying.
- The platform-hosted playback was checked on relevant devices.
Frequently asked questions
Can one MP4 be uploaded to every platform?
One file may fall inside several platforms’ technical limits, but that does not make it the best composition everywhere. Use one approved master and create destination-specific landscape or vertical versions when the viewing experience, crop, captions, or call to action requires them.
Should I export vertical video at 9:16?
Use 9:16 when the intended experience is a full-screen vertical placement such as Reels or Shorts. Confirm the current destination guidance and preview the published result because interface controls and cover crops can affect the visible area.
Should the export frame rate be 30 or 60 fps?
Preserve the source frame rate unless the workflow has a tested reason to change it. YouTube explicitly recommends uploading at the same frame rate used for recording. Unnecessary conversion can introduce judder or duplicated frames.
Are platform limits the same for organic posts, ads, and APIs?
No. A platform can publish different limits for member uploads, advertising products, and API-based publishing. Document the exact publishing path and verify the official specification for that path.
Should captions be burned into the video?
It depends on the destination and control required. Burned-in captions remain visually consistent but cannot be turned off and need crop-safe placement. Separate caption tracks can provide more flexibility when supported. In either case, review the final text and timing.
What should I do after an upload timeout?
Do not immediately submit a differently named copy. First reconcile the destination using the expected post, upload, media, or schedule identity. Retry only when provider state shows the original operation did not succeed.
How do I verify that recompression did not damage the product video?
Compare the platform-hosted playback with the approved delivery file. Review fine labels, edges, gradients, fast motion, captions, audio synchronization, and the end card on the devices viewers will use.
What evidence should the team retain?
Retain the approved master revision, delivery manifest, exact file identity, platform or upload ID, public URL, approval record, verification time, and any exception. Keep credentials, signed URLs, and private customer data out of editorial records.
Final takeaway
A reliable export workflow protects the creative decision all the way to published playback. Preserve one approved master, reframe deliberately for each important layout, follow the official requirements for the exact publishing path, and keep evidence for every delivery file. Most importantly, verify what the audience can actually watch. That final check catches the failures an export-complete message cannot.
About VideoPopy Editorial Team
The VideoPopy editorial team documents practical AI video workflows, product limitations, and publishing checks using the product and primary platform guidance.
Read our AI content policy