Automatic MIME Type Detection Now Available on AIOZ Storage

TL;DR

• Automatic MIME type detection for S3-compatible uploads
• Detects file type from content when Content-Type is missing
• Stores detected type as object metadata
• Powered by Google Magika
• Adds reliable fallback without changing existing workflows

What This Feature Does

AIOZ Storage now supports automatic MIME type detection, powered by Google Magika.

For S3-compatible uploads, file types are detected from content when Content-Type is missing, helping ensure objects carry consistent metadata from upload through to delivery.

Why MIME Type Detection Matters

MIME type detection helps storage systems understand what kind of file has been uploaded. When upload metadata is missing or inconsistent, developers may need to handle classification issues manually. Automatic detection gives AIOZ Storage a more reliable fallback, especially when file extensions or client-provided metadata are incomplete.

Object metadata determines how files are classified and handled after upload. Browsers, applications, and delivery layers rely on MIME type to interpret content correctly. When metadata is missing or inaccurate, files can be harder to serve or process consistently.

Automatic MIME type detection improves this part of the workflow by adding:

• Content-based MIME detection during upload
• More reliable handling for files with missing or misleading extensions
• More consistent object metadata
• Stronger fallback behavior across multi-source uploads
• More accurate classification when content and filenames do not align

How AIOZ Storage Handles Upload Metadata

AIOZ Storage follows a priority-based upload flow:

If an upload request includes a Content-Type header, AIOZ Storage uses that value as the object’s MIME type. If it is missing, the file type is detected from content and stored as object metadata.

The flow works like this:

1. A file is uploaded through an S3-compatible workflow.
2. AIOZ Storage checks whether Content-Type is provided.
3. If it is provided, AIOZ Storage uses that value.
4. If it is missing, AIOZ Storage detects the MIME type automatically.
5. The final MIME type is stored as object metadata.
6. That metadata is used when the object is served later.

This keeps the upload pattern familiar. Developers can still provide explicit metadata when they want control, while AIOZ Storage adds smarter defaults when metadata is incomplete.

It also fits the broader role of AIOZ Storage as S3-compatible object storage for application workflows. Files may be uploaded by users, services, tools, or automated pipelines. When metadata quality varies across those sources, automatic MIME type detection helps keep the storage layer more consistent.

When This Feature Helps Most

This feature is especially useful in workflows such as:

• User-uploaded media libraries
• Document storage systems
• Multi-client upload workflows
• Application pipelines using S3-compatible storage
• Services where upstream metadata may be incomplete
• Workflows that need more consistent object classification after upload

Try It on AIOZ Storage

Automatic MIME type detection gives AIOZ Storage a cleaner default for S3-compatible upload workflows.

Provide Content-Type when you want explicit control. When it is missing, AIOZ Storage can detect the file type from content and store the result as object metadata.

Start using it in your S3-compatible uploads and see how your object metadata behaves with more consistent defaults.

FAQ

Q1: What happens if I provide a Content-Type header?

AIOZ Storage uses the Content-Type value provided in the upload request.

Q2: Does this change S3-compatible upload workflows?

The upload workflow remains S3-compatible. The feature adds automatic detection when upload metadata is incomplete.

Q3: Why does object metadata matter after upload?

Object metadata determines how files are classified and served, affecting application behavior, browser handling, and delivery workflows.