Video Merger.

  • each::labs
  • Video to Video
  • $0.00185 per processing second
  • ~2 min average

Video Merger joins multiple clips into one continuous video in a single call, stitching footage together in your chosen order and resolution.

What Video Merger is good at.

  • Best for

    Video Merger is useful when this specific operation fits between source preparation and delivery.

    These scenarios show how it can support different parts of a working pipeline.

  • Limits and tips

    Getting good results

    Keep an untouched source file and verify its duration, dimensions and streams before choosing edit settings. Make one small representative request, inspect the…

  • Related model

    Google | Gemini Omni 1.2 Flash | Video Upscale

    Run it on the same input to compare output, speed and price.

    View model

Model documentation

About this model

Video Merger joins multiple clips into one continuous video in a single call, stitching footage together in your chosen order and resolution.

Overview

Video Merger Overview

Video Merger joins multiple clips into one continuous video in a single call, stitching footage together in your chosen order and resolution.

The first and second clip inputs define the merge order and the output dimensions.

Video Merger is available through each::labs in the Video-API family. Required fields are first_clip, second_clip, width, height.

The operation uses the supplied source to perform its specific task. It can be placed between source preparation and final delivery without combining unrelated changes into the same request.

Use the Video Merger API when you need this transformation or analysis as a repeatable step in an application or creative pipeline. The sections below distinguish the required material, adjustable controls and checks that matter before delivery.

Capabilities

Capabilities

  • The first and second clip inputs define the merge order and the output dimensions.
  • first_clip: URL of the first source video clip to merge.
  • second_clip: URL of the second source video clip to merge.
  • Produces a video result for the next stage of your workflow.
  • Runs the requested operation on the supplied input rather than requiring a manual editing session.

Use cases

Use Cases for Video Merger

Video Merger is useful when this specific operation fits between source preparation and delivery. These scenarios show how it can support different parts of a working pipeline.

Creators

Join an introduction to a demonstration. Use a representative source or a concise brief, then inspect the result before preparing a larger set of assets.

Design and marketing teams

Assemble a two-shot preview. Compare the result with the intended message, composition and destination. Keep reviewable versions of the source and output.

Developers

Combine related lesson clips. Inspect the actual returned value before connecting it to another step, and keep the chosen request settings with the result.

Start with a clear definition of the desired result and use the exposed controls to reach it. Keep any additional generation, editing or application logic in separate steps so that the effect of this operation remains easy to review.

Tips & tricks

Tips and Tricks

Keep an untouched source file and verify its duration, dimensions and streams before choosing edit settings. Make one small representative request, inspect the returned asset, and use the same settings only when they fit the remaining material.

Choose a representative source for the first pass. Keep the original material and record the request values so that a successful result can be reproduced as part of your wider editing or processing sequence.

Set the named operation controls directly. This entry has no general creative-prompt interface; supplying an invented prompt field will not replace a required source or numeric setting.

Compare one deliberate adjustment at a time. Inspect the part of the result affected by that change, then check the rest of the asset or response for unwanted side effects before reusing the settings.

Technical spec

Technical Specifications

  • Result type: video.
  • Required fields: first_clip, second_clip, width, height.
  • width: integer; minimum 0.
  • height: integer; minimum 0.

first_clip: URL of the first source video clip to merge.

Values must use the types and accepted options listed in the parameter reference. A displayed default does not remove a required-field requirement. Choose a supported output setting for this entry rather than borrowing a preset from a related model.

Things to be aware of

Things to Be Aware Of

Check the processed asset in the actual destination player or editor. Review the opening, closing, sound, crop and any transition points relevant to this operation instead of assuming a successful job proves the edit is correct.

Optional settings are not necessarily interchangeable with those on another entry in the same family. Use the accepted names, types and values shown for this operation.

For media-based inputs, supply a directly retrievable file URL rather than a page containing the asset. Keep the source available while processing. Check the final content in the destination player, editor or application, not only the request status.

Key considerations

Key Considerations

This row exposes two source clips, not an arbitrary list; inspect the join and sizing when sources differ.

Public estimate: $0.00185 per processing second.

Prepare first_clip, second_clip, width, height before starting. Keep these settings aligned with the intended delivery, especially when a later step expects a particular type or format.

Run a representative request before scaling to a larger collection. Judge the result against the source and the brief, and account for all generated outputs or usage-sensitive options when estimating a batch.

Limitations

Limitations

  • width: minimum: 0.
  • height: minimum: 0.

Unsupported parameters do not establish additional capabilities. Source quality and the chosen settings constrain what a processing step can deliver. Keep the source and check the result before replacing a final asset.

Questions about this model

The short answers. For anything specific to your setup, talk to our team.

Talk to an engineerPlan for your expected volume.
  • Video Merger joins multiple clips into one continuous video in a single call. On the each::labs Video API it stitches your footage together in the order you set, producing a single seamless file from separate sources.

Ready to close the gap?

Find the model. Build the workflow. Ship the result.