↓
Rivya AI Docs

Rivya Reference Files and Upload Requirements

Choose compatible image, video, or audio references, check model-specific upload rules, and keep originals and API metadata for reuse.

Last reviewed on November 5, 2026

Start with the model and operation you plan to use. Check the model page and its current availability, then confirm the accepted file types, per-file size limit, reference count, dimensions, and any duration requirements before uploading.

Match Your Reference to the Operation

What you want to doWhat to check
Use a product photo or another image as a referenceCheck image-to-image support, reference count, and each image's role; see image workflows
Animate an image, guide motion, or modify a videoCheck whether the operation accepts an image, a video, or a permitted combination; see video workflows
Use an existing recordingCheck the specific operation's audio input requirements before providing a recording; see audio workflows
Ask a chat model about an imageCheck current image-attachment support separately from model availability

Rivya's currently available chat models accept text only. The chat interface is not a general PDF, spreadsheet, video, or audio uploader. For an existing conversation, open the correct saved session before continuing.

ElevenLabs Audio Isolation is paused, and Rivya currently has no direct available replacement for cleaning an uploaded recording. Suno Sounds creates new sounds; it does not clean your recording. An audio input listed on an unavailable model page is not a runnable feature.

Check the Selected Model's Limits

Check the selected model's upload requirements for its per-file size limit and accepted formats. The formats below are default uploader policies; model-specific rules can narrow or expand them and add other checks.

File kindOther checks to confirmDefault accepted formats
ImageDimensions, aspect ratio, and reference countJPEG, PNG, WebP
VideoDuration, dimensions, frame rate, and bitrate where requiredMP4, MOV / QuickTime, WebM
AudioDuration and the recording's role in the selected operationMP3, M4A / MP4 audio, WAV, AAC, OGG

Image tools have different limits. Compare the input requirements for Nano Banana 2, Nano Banana Pro, and Recraft Remove Background. Check the selected model's size, format, and reference-count requirements before preparing files.

For Wan 2.6, use either image or video references in a request. Its image and video modes have separate count, format, and dimension rules. Check the chosen mode's requirements before uploading.

A file can be below its size limit and still fail a dimension, aspect-ratio, duration, or format check. Rivya checks the actual file format; renaming an extension does not convert a file. Mode-specific and total reference limits still apply even when each file is valid.

Upload and Submit in the Right Order

  1. Confirm the target model is runnable, select its operation, and check the file requirements. Keep original files locally and prepare only what the task needs.

  2. Sign in before uploading. If the model's public form supports the input, you can use it there after sign-in or continue in the Studio. Review the login and draft guide before leaving an unsent draft.

  3. Upload through the selected model's form and wait for completion. Check the file names, count, and any role labels in the reference list. Confirm which files were added; excess or rejected files can be missing.

  4. Write the prompt, check the selected settings and estimated credits, then submit once. An upload finishing does not itself start a generation. The credit guide explains reservation and final settlement.

  5. Review the result against your references. If you change model or mode, check the settings and references again; some may be reset, removed, or no longer valid. Re-upload originals in the new form when needed.

Give Each Reference a Clear Role

Use a clear image for the subject and explain the intended change. If the model supports multiple references, distinguish the subject, style, background, or motion source instead of asking every file to control everything.

For a product-photo edit, you could write:

Use the uploaded bottle as the product reference. Keep its silhouette, cap, and label layout. Replace the background with a pale grey tabletop and add a soft shadow. Do not add text or extra objects.

This is an example instruction, not a tested result or a guarantee of preservation. Check the bottle's proportions, label text, logo, and edges yourself. A reference can guide generation without preserving exact geometry or typography; prepare final brand assets in an editor if accuracy requires it. See choosing a reference-image generator for comparison criteria.

Remove unrelated personal or client information before upload and use files you are entitled to provide. The safe-upload guide covers preparation in more detail.

Fix Rejected or Missing Uploads

ProblemNext step
No upload control is shownCheck sign-in, model availability, the selected operation, and accepted input kinds. Use a model that supports the reference
File is too largeExport a smaller copy within that model's limit while preserving any required dimensions or duration
Format is rejectedRe-export in an accepted format; changing the filename extension is not enough
File fits the size limit but is rejectedCheck dimensions, aspect ratio, duration, and any additional media requirements. Open the original file locally to confirm it works
Some selected files are missingCheck per-kind and total counts and allowed combinations; upload only the files needed for this mode
Upload stalls or failsWait for the upload to complete or fail, then check the reference list and retry only missing files. Check an already-submitted generation before sending it again

If the error persists, follow troubleshooting. Keep the model name, file format and size, error message, and any task identifier. Do not post private files, access links, verification codes, or API keys in a public support request.

Keep Originals and Preserve API Metadata

Keep original files and a local note of important prompts and settings. Use History to find saved tasks and download results you want to keep. Reference URLs and result links can expire; a history entry does not guarantee that every file remains accessible. Unsent drafts are not saved tasks in history.

For an integration, follow the Files API and the target model API reference. Uploading requires an API key with files:create; reading an owned file record requires files:read. The model must also be available for the requested API input.

When a model requires a signed upload, upload the original for that target model and keep the complete successful response. Preserve the returned URL, MIME type, byte size, dimensions, duration, and signed fields together as required by the model's contract. Re-upload the original for the target model if required metadata is missing or expired.

A file record's expires_at value of null does not guarantee that its remote URL remains available. Retrieving the record does not restore the full original upload response or check whether the remote file still downloads. Keep your originals and the successful upload response for reuse.