Choose an input file supported by the specific Creative APIs endpoint you call, and request an output format suited to your destination. Input support does not imply output support, and format limits do not replace API limits.
Input and output checklist
The Creative APIs image-format guide lists JPG, PNG, WEBP, TIFF, BMP, MPO, MJPEG and HEIC/HEIF inputs, with a general 100 MB file-size ceiling. Individual services can impose stricter limits on file size, dimensions, pixels or format variants. Check the selected endpoint before uploading.
Common image endpoints offer JPG, PNG and WEBP through the format parameter. Defaults differ between services. Do not request TIFF or HEIC output unless the endpoint explicitly lists it.
The source guide describes uploaded and result files as available for 24 hours. Download results promptly to storage you control rather than relying on an API/CDN URL as permanent hosting.
Choose the output format
- JPG/JPEG: useful for photographs when lossy compression is acceptable. It does not preserve a transparent background. Repeated lossy saves can reduce quality.
- PNG: lossless compression and transparency, useful for cutouts, logos and graphics. File size depends on the image.
- WebP: supports lossy or lossless compression and transparency. Check the receiving application and use the options exposed by your endpoint; no fixed size reduction is guaranteed.
- TIFF: used for high-quality source images and print/archival workflows. Compression, pages, layers and metadata vary. A TIFF input does not guarantee every page, layer or tag survives processing.
- BMP: a raster image format that may produce large source files.
- MPO: can hold multiple JPEG images, including stereoscopic views and related metadata. Do not assume an API processes or preserves every view. Extract the required image when necessary.
Compare an exported sample at its intended display size. Inspect detail, color, transparency and file size rather than relying on a universal quality percentage or theoretical maximum resolution.
RAW camera files
RAW files contain camera sensor data and need a compatible RAW developer. Camera support depends on the model and file variant, not just the extension. Creative APIs does not list camera RAW among the general image inputs; develop a copy into a supported format first and keep the original.
Common families include Canon CR2/CR3; Nikon NEF/NRW; Sony ARW/SRF/SR2; Olympus ORF; Panasonic RAW/RW2; Fujifilm RAF; Adobe DNG; Leaf MOS; Kodak KDC/DCR; Sigma X3F; Pentax PEF; Hasselblad 3FR/FFF; Mamiya MEF; Epson ERF; Phase One IIQ; and Leica RWL. Blackmagic BRAW and Phantom CINE belong to camera/video workflows and should not be treated as ordinary still-image inputs.
See Convert RAW to JPEG for the preparation workflow.
MJPEG versus a still JPEG
Motion JPEG encodes video frames individually as JPEG images. It can occur in a media container or stream. A still JPEG may also appear as codec mjpeg in FFprobe output; an assumed frame rate such as 25 fps is not proof that the file contains motion.
Inspect the file’s actual frames, duration and container, not its extension alone. For example, ffprobe original.jpg can report the encoding. Check frame count and playback before concluding that it is a video. Support for JPEG decoding in an image endpoint does not establish support for an MJPEG stream or every MOV/MP4 container.
HEIF, HEIC and Live Photos
HEIF is a container format; HEIC commonly identifies HEVC-encoded still images. The image endpoints listing HEIC/HEIF support should be used with the still image. Do not infer support for arbitrary sequences, depth metadata or a complete Live Photo from still-image support.
A Live Photo includes a still and a paired video component. Export the still from your photo library and submit that image to an image endpoint. Treat the video separately. Do not rely on the old guide’s “HEIV” label as a supported Live Photo upload format.
Check that the exported file is readable and uncorrupted. If a receiving application needs JPEG, PNG or WebP, request a supported output format and inspect the result.
If an upload fails
- Check the selected service’s input formats, dimensions and file-size limits.
- Verify the actual file contents; renaming an extension does not convert it.
- For URL input, ensure the API can retrieve the image rather than a login page or expired link.
- Export a compatible still-image copy, test one request and inspect the response before processing a batch.
Related help: Supported image formats and Image resolution and file size.