Upload File Limitations

API version: v1.2.4

Prepare reference images for MiniMax H3 Standard and Turbo, and check the separate requirements for supported LoRA uploads. The sizes below are published defaults; active account or service limits can differ. A successful upload does not establish that a file meets a generation model's input requirements.

Image Upload (/api/v1/storage/image/upload)

File Constraints

Recommended Specifications

Choose a clear source image with the subject and framing you want to animate. Prepare any resizing, color conversion or background changes before uploading. For H3, choose resolution_tier and aspect_ratio when submitting generation; see video generation limits for dimensions and reference requirements. File size and output resolution are separate constraints.

Use upload an image for a local file or import an image for a public image URL. Both guides include H3 Standard and Turbo examples.

Validation Rules

• Supply a nonempty file with a supported extension and recognizable image content.
• Keep the filename consistent with the image format.
• Check the selected model's reference requirements before generation.
• Do not depend on automatic color conversion or transparency flattening.

LoRA Upload (/api/v1/storage/lora/upload)

File Constraints

The active size limit applies to the sum of both files. LoRA upload is a separate workflow; it does not imply that every generation model accepts custom LoRAs.

Metadata Constraints

See the LoRA upload contract for supported metadata fields and their types. Check the response for validation errors rather than assuming universal name, description or tag-length allowances.

Processing Time

LoRA uploads are processed asynchronously. Keep the returned lora_id and use LoRA status to check readiness or failure. Completion time depends on the request; this page does not specify a processing-time guarantee.

Rate Limits

For request throttling, HTTP 429 responses include Retry-After, X-RateLimit-Limit and X-RateLimit-Window headers. Wait for the indicated interval before retrying. See the common API contract.

LoRA storage-capacity limits can also return 429; read the error response before deciding whether waiting or removing an existing model is appropriate.

Storage Quotas

Storage capacity and retention depend on the resource and active account policy. Check LoRA upload and LoRA status for retention details. Contact Phosor support for account-specific capacity questions.

Error Examples

File Too Large (Image)

The image upload endpoint returns HTTP 400 for a file rejected by its active size limit. Read error and message in the response; message text can vary. Reduce the file size before trying again. Image import is a separate endpoint; see its error guidance.

File Too Large (LoRA)

HTTP 413 includes a detail message describing the combined file size and active maximum. Reduce the combined size of the two files.

Invalid Format

Use JPEG, PNG or WebP for image upload and .safetensors for both LoRA files. LoRA format errors return HTTP 400 with a detail message. Read each endpoint's error response rather than assuming they share an identical body.

Missing Required File

Image upload requires the multipart field image. LoRA upload requires both high_noise_file and low_noise_file; missing required form fields return a validation error. See each endpoint's request table for the exact field names.

Invalid Image

Check that the file is nonempty and contains recognizable image content with a matching filename. A successful upload is separate from model validation. After H3 submission, keep the returned request_id to check request status and retrieve the result. Compare MiniMax H3 Standard and Turbo before choosing a mode.