# Why should I set a content type when saving an object?

Canonical URL: https://help.iagenify.com/faqs/object-storage/why-should-i-set-a-content-type-when-saving-an-object

[← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)

HELP CENTER · FAQ Object Storage 2 min read
# Why should I set a content type when saving an object?
The content type tells readers what kind of data the object contains. Set it when the format is known so later tools can interpret or serve the file appropriately.
IaGenify
Object Storage

## Describe the bytes you saved
A filename extension can suggest a format, but it is not always enough for software that reads an object. The content type is metadata attached when saving and may be returned with the object's key and size. Choose a value that accurately describes the bytes, such as a text, image, or application format supported by the consuming tool.
Do not label content based only on the intended use or file name. If encoded binary data is decoded incorrectly before saving, a correct content type cannot repair the stored bytes. Confirm both the saved data and the metadata match the format the next step expects.
## Check how downstream readers use the metadata
A later workflow step or browser may use the content type to decide how to parse, preview, or download an object. If the type is missing or inaccurate, a reader might treat valid data as unknown or interpret it incorrectly. The behavior depends on the client, so test with the actual consumer.
Save a small sample, retrieve it through the same path the application will use, and inspect its content type and contents. When the format is uncertain, retain the original data and verify it with a suitable parser before changing metadata. Avoid using an executable or active-content type unless that is truly what the file contains and the access policy allows it. [← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)