Multimodal & Media
When your traces include images, audio, video or documents, ANTS Platform stores the files and shows them inline, so you can review exactly what went into and came out of a call.
ℹ
Media has no page of its own. It appears in the Preview of a trace or observation, in a Media section under input, output or metadata.
Supported types
| Kind | Content types |
|---|---|
| Images | PNG, JPEG, WEBP, GIF, SVG, TIFF, BMP |
| Audio | MP3 (audio/mpeg), WAV, OGG, AAC, M4A (audio/mp4), FLAC |
| Video | MP4, WEBM |
| Documents and data | PDF, plain text, HTML, CSS, CSV, JSON, XML, Word (application/msword), Excel (application/vnd.ms-excel), ZIP, and other binary files (application/octet-stream) |
Images render inline, audio and video get a player, and other files open in a new tab.
How it works
- The Python and JS/TS SDKs detect base64 data URIs and wrapped media objects
in input, output and metadata. In Python, media upload is on by default and
can be turned off with
ANTS_PLATFORM_MEDIA_UPLOAD_ENABLED=false. - The SDK registers each file with
POST /api/public/media, giving its content type, size and SHA-256 hash, and uploads it to object storage with a short-lived upload URL. Files with the same hash are stored once per project. - The trace stores a reference to the file instead of the raw bytes.
- In the trace view, ANTS Platform resolves each reference to a temporary signed URL and renders the file.
You can also call the media endpoints yourself. See the API Reference.
Limits and deployment
- The default maximum file size is 1 GB. Self-hosted deployments can change it.
- Media needs an object storage bucket for media to be configured on the deployment. Without one, media upload fails.
- Signed URLs expire. Only users who can open the trace can see its media, unless the trace is shared publicly.
- See Data Retention for how long attachments are kept.
Next steps
- Traces & Observations: where media renders.
- Sending Data In: instrument your application.
- Data Privacy: storage and access considerations.