Generic Binary Data MIME Type

What does application/octet-stream mean?

The application/octet-stream media type says that a body contains arbitrary binary data. It describes the bytes only in the broadest sense. It does not identify a particular document, archive, executable, image, or other file format.¹²

That distinction matters. A server might use application/octet-stream because the payload truly has no more specific registered type, because its software could not recognize the format, or because it wants a browser to download the response instead of displaying it. The label alone cannot tell you which case applies.

Does application/octet-stream have a file extension or magic number?

No standard extension or magic number belongs to application/octet-stream. The IANA registry points to the MIME specifications rather than defining a format-specific registration template.¹ Any byte sequence can carry this type, so no fixed signature could identify every valid payload.

You may see .bin, .dat, or a format-specific extension on a downloaded response. Those names are conventions or clues about the underlying content, not extensions registered to application/octet-stream. A .bin file could be firmware, a disk image, an executable, serialized data, or something proprietary.

Poly's own implementation illustrates the ambiguity. It recognizes application/octet-stream as a canonical media type but gives it no canonical extension. Poly currently maps .dll and .elf filenames to this fallback when it does not assign a more specific type. That behavior is an application choice, not a standard association.

Why do browsers download application/octet-stream responses?

RFC 2046 recommends offering to save the data to a file or passing it to a process chosen by the user.² Current browsers follow the same basic safety model. They generally treat application/octet-stream like an attachment and present a download or Save As workflow instead of trying to execute or render unknown bytes.³

For HTTP downloads, Content-Disposition can provide the intended handling and suggested filename. For example:

Content-Type: application/octet-stream
Content-Disposition: attachment; filename="payload.bin"

The filename value is only a suggestion. RFC 6266 warns recipients to discard path information, avoid dangerous names, and prevent accidental overwrites.⁴

How to identify and open an octet-stream download

Start with context rather than guessing an application:

1. Check the original filename, source, download page, and any accompanying documentation.
2. Inspect the HTTP Content-Disposition filename if one was supplied.
3. Use a file-identification tool to examine the contents.
4. Open the file only after you have identified its actual format and trust its source.

On macOS, Linux, and other POSIX-style systems, the file utility examines file metadata and an initial portion of the bytes. It applies position-sensitive tests, often called magic-byte tests, and context-sensitive tests. POSIX is explicit that the result is a guess and is not guaranteed to be correct.⁵

file downloaded.bin

A hex editor can help when file reports only data. Compare the opening bytes with the authoritative specification for the suspected format. Some formats have no signature, multiple signatures, or a header shared with related formats, so magic bytes are evidence rather than proof.

Support in Poly

Poly can store, sync, share, version, and download files labeled application/octet-stream. The type also serves as Poly's fallback when neither the filename nor an initial byte inspection yields a recognized format. Plain UTF-8 content is classified as text instead, while recognizable images, audio, and video can be assigned their specific media types.

Generic binary files remain in Poly's unknown media category. They are searchable by filename and ordinary file properties, but Poly does not:

• Parse or extract the binary contents.
• Generate a format-specific thumbnail.
• Provide an in-app content preview.
• Make the opaque bytes readable to the Poly agent.

Download the file and determine its real format when you need richer handling. Correcting an inaccurate extension may let Poly identify a supported format on a later import, but renaming a file does not convert its contents.

Can you convert application/octet-stream to PDF, JSON, or another format?

Not from the MIME label alone. Conversion requires knowing the source encoding. The same media type can stand in for a PDF, executable, compressed archive, custom database, or random byte sequence, and each requires a different decoder.

A safe conversion workflow is:

1. Identify the actual format from trusted context and byte-level evidence.
2. Validate the file with a parser designed for that format.
3. Use that format's documented export or conversion tool.
4. Assign the specific registered media type to the result.

Renaming payload.bin to payload.pdf changes only the filename. It does not add a PDF header, parse the original data, or make the bytes valid PDF.

History and standardization

The original MIME specification, RFC 1341, defined application/octet-stream in June 1992.⁶ The current IANA registry cites RFC 2045 and RFC 2046, published in November 1996.¹ RFC 2046 retained the arbitrary-binary meaning and the optional type and padding parameters. It removed the earlier conversions parameter and deprecated the earlier name parameter in favor of a separate Content-Disposition field.²

The media type remains useful because protocols need a conservative fallback. Modern MIME sniffing rules likewise compute application/octet-stream when bytes appear binary but do not match a known signature. The WHATWG standard deliberately avoids turning such unknown data into a scriptable type, which helps prevent content-sniffing attacks.⁷

Is application/octet-stream the same as application/zip?

No. application/zip identifies a ZIP archive. application/octet-stream does not identify any specific structure.

A ZIP file can be mislabeled as application/octet-stream and still contain valid ZIP data. Changing its Content-Type to application/zip describes those bytes more accurately, but does not modify the archive itself.