Papiboom Studio

GUIDE / REFERENCE MEDIA

Why is my reference image
not working in AI video?

Trace the reference path from upload and media readability to model compatibility, selected node output, and prompt direction.

No subscription required / Pay-as-you-go credits

Fashion-oriented AI video frame guided by a connected image reference Cinematic AI video frame created with connected visual references Product motion frame generated from a reusable reference workflow
UploadConfirm that the complete source reaches the workspace.
ReadVerify that the browser and service can decode the media.
MatchChoose a model that accepts the source type and role.
DirectTell the model what the selected reference should control.

Five reproducible input checks.

These synthetic examples were checked against Papiboom's local request validators on October 12, 2026. A pass means this input-contract check passes, not that upload, provider moderation, generation or output quality has been tested. No generation output or acceptance rate is claimed.

Model and settings
Rejected input
Single correction
Local check
Happy Horse 1.1: 5s, 720p, 16:9
2 images and 1 video
Remove the video; retain 2 images
Rejects mixed video; image-only set passes
Happy Horse 1.1: 5s, 720p, 16:9
10 image references
Reduce to 9 images
Rejects excess images; 9 passes
Seedance 2.5: 5s, 720p, adaptive
Last frame only
Add the first frame
Rejects missing first frame; first + last passes
Seedance 2.5: 5s, 720p, adaptive
First frame and general image reference
Keep frame mode only
Rejects mixed modes; first frame alone passes
Seedance 2.5: 5s, 16:9, 1 image
2160p output
Select 1080p
Rejects unsupported resolution; 1080p passes

Happy Horse 1.0 and 1.1 have different input contracts. Do not infer video support from the family name. For a new project, start with the reference-led test brief; compare Seedance versions before choosing. Fewer restrictions concerns filtering, not these input requirements.

/ Papiboom editorial

A reference passes through more than one check.

An image can appear in a project and still fail at generation. Upload storage, media decoding, node selection, reference role, model limits, and prompt direction are separate parts of the path.

Direct answer

A reference image may not work because the file did not finish uploading, cannot be decoded, is connected from the wrong node output, uses a role the selected model does not support, exceeds that model's limits, or reaches the model without clear direction. Seeing a thumbnail only confirms one part of that path.

01 / UPLOAD

Uploaded is not model-compatible

A stored file can still use an unsupported format, size, duration, dimension, media type, or input combination.

02 / ROLE

Reference roles are not interchangeable

A style image, first frame, motion video, and audio source travel through different model controls.

03 / OUTPUT

The selected result matters

When a connected node has several outputs, Papiboom sends the currently selected history result downstream.

Start with the stage where it stops.

The visible symptom narrows the failing layer. Fix that layer before changing every prompt, model, and source at once.

Observed symptomLayerWhat it suggestsFirst check
Upload never completes
Transport

The workspace has not received a usable source

Check connection, size, file type, and visible upload progress
Thumbnail or source will not open
Media readability

The upload exists but cannot be decoded or materialized

Open the asset directly and try a standard export
Immediate validation error
Input contract

The selected model does not accept that role or combination

Check media type, count, frame mode, duration, and required inputs
Task ID, then failure
Model or provider

The request reached generation but the upstream task rejected or failed

Preserve the task ID and read the specific failure reason
Output ignores the source
Direction

The media arrived but its intended role was unclear or weak

Select the intended output and describe the source role explicitly

Choose the reference role before the model.

The same file can be valid in one role and invalid in another. Decide whether it should define appearance, frame boundaries, motion, or sound.

Reference roleUsually controlsHow to use itCommon mistake
Image reference
Subject, character, product, composition, or style context

Use a model that accepts images; state what should remain consistent

Treating the image as a guaranteed pixel-for-pixel copy
First / last frame
The opening composition and optionally the closing composition

Add the first frame before the last; keep frame mode separate from mixed-reference mode

Mixing frame mode with a separate multimodal-reference set
Video reference
Motion, timing, camera behavior, or multimodal scene context

Use a model that accepts video and keep the source within its duration and size limits

Sending video to a text-or-image-only model
Audio reference
Voice, music, rhythm, ambience, or timing context

Use an audio-capable model; some models also require a visual source

Adding audio without the visual source required by the model

Current Papiboom reference contracts.

These limits reflect the current Papiboom integrations as reviewed on October 12, 2026. Model contracts can evolve, so the live model card remains the final check before submission.

ModelOutput rangeAccepted referencesImportant condition
Seedance 2.5
4-30s / 480p-1080p

Up to 30 images, 10 videos, and 10 audio files, or first + last frame

Frame mode requires adaptive aspect and first before last; do not mix with general references
Seedance 2.0 Mini
4-15s / 480p-720p

Up to 9 images, 3 videos, and 3 audio files, or first + last frame

Last frame requires first; frame and mixed-reference modes are separate
MiniMax H3
4-15s / 2K

Up to 9 images, 3 videos, and 3 audio files, or first + last frame

Audio needs a visual source; video and audio duration totals are limited
Kling 3 Motion Control
3-30s / 720p-1080p

Exactly 1 character image + 1 motion video

Duration follows the usable motion clip; this is not a general mixed-reference mode
Happy Horse 1.1
3-15s / 720p-1080p

Up to 9 image references

No video, audio, or first/last-frame input in the current integration
Grok Imagine 1.5 Preview
1-15s / 480p-720p

Up to 1 image reference

No video, audio, or first/last-frame input in the current integration

An eight-step reference check.

Use one known-good source first, then add complexity one item at a time. This preserves a working baseline and reveals the exact incompatible input.

01

Open the source

Confirm the image, video, or audio plays outside the node and has finished uploading.

02

Choose its role

Decide whether it is a general reference, first or last frame, motion source, or audio source.

03

Match the model

Check that the selected model accepts that media type, role, count, duration, and combination.

04

Connect one source

Begin with a single authorized reference and confirm that its capsule appears on the generation node.

05

Select the right result

If the source node has history, click the exact image, video, or audio output you want to send.

06

Direct it clearly

A connected source is submitted without an @ token, but @ can clarify which source controls subject, style, action, or framing.

07

Add sources gradually

Reconnect the remaining media one at a time so count, duration, or mode conflicts are visible.

08

Keep the error evidence

Preserve the exact message and task ID when the request reaches generation but still fails.

Use predictable media exports.

Standard formats reduce browser and provider decoding surprises. They do not override a model's own size, duration, dimension, or content limits.

Practical starting formats

Use broadly supported exports before investigating a model-specific problem.

  • Images: JPG, PNG, or WebP
  • Video: MP4 with H.264 video
  • Audio: MP3 or WAV
  • Open the final export locally before upload

Then check the contract

Every generation model can apply narrower constraints.

  • Maximum source count and file size
  • Video or audio duration limits
  • Required first frame or visual source
  • Frame mode versus multimodal-reference mode

AI video reference questions.

Short answers for references that upload, connect, or generate differently than expected.

Why is my reference image not working in AI video generation?

A successful upload only proves that the workspace received the file. The selected model must also accept that media type, reference role, file properties, and combination of inputs.

Do I need to type @image in the prompt?

In Papiboom, a connected reference is submitted even when no @ token appears in the prompt. An @ reference token is useful when you want to state clearly which source controls the subject, style, action, or another part of the scene.

Can I use a video as a reference?

Only when the selected model accepts video references. Motion Control is a separate input contract that requires exactly one character image and one motion video rather than a general multimodal reference set.

Why does an end frame fail?

Models with frame control require a first frame before a last frame. In the current Papiboom integrations, frame mode is also kept separate from multimodal-reference mode.

Which output is used when a node has several results?

Papiboom sends the currently selected node-history result to a connected downstream node. Select the intended image, video, or audio result before running the next generation.

Which reference formats are safest to use?

JPG, PNG, or WebP are practical image choices; standard MP4 with H.264 is a practical video choice; and MP3 or WAV are practical audio choices. Model-specific size, duration, and dimension limits still apply.

Keep diagnosing with the exact layer.

If the media path is healthy, continue with the broader failure checklist or compare the live input contracts before moving the same sources to another node.

A reference failed elsewhere?

Bring the prompt and authorized image, video, or audio reference to Papiboom. Connect each source visibly, choose a compatible model, and retry without rebuilding the workflow. Model capabilities, Papiboom rules, and applicable law still apply.

Try a reference workflow