1.  [](/)
2.  [Diagrams](/diagrams)
3.  S3 stores bytes, not answers

[Back to Diagrams](/diagrams)IR Foundations

# S3 stores bytes, not answers

Storage keeps the bytes; an index keeps the meaning: the archive is only useful once it is indexed.

![Storage versus index: object storage like S3 preserves the raw bytes durably but can never answer a question about what is inside them, while an index reads the content once, extracts what it means, and remembers it so queries get answered in milliseconds without re-reading everything. Without an index, every added terabyte raises the storage bill while the number of answerable questions stays flat at zero.](/diagrams/foundations/storage-vs-index.webp)Full screen

Storage keeps the bytes; an index keeps the meaning: the archive is only useful once it is indexed.

There's a category error I see constantly: teams assume that because data is stored, it's available.

S3 will keep a petabyte of video safe for decades, replicate it across regions, serve any byte on demand. What it will never do is answer a question. Storage preserves bytes. Only an index makes them findable. Those are different jobs, and the industry has spent 15 years perfecting the first one while mostly ignoring the second for anything that isn't text.

So the archive grows, the storage bill grows, and the usefulness of the data stays flat at zero until something reads it once and remembers what it found.

That layer is the entire bet behind Mixpeek: extract meaning on ingest, index it next to the bytes, answer questions forever after.

Storing data is a solved problem. Knowing what you stored isn't.

## Where this diagram appears

*   [Glossary: Indexing (Multimodal) →](/glossary/indexing-multimodal)

Run this on your own data

Mixpeek turns video, images, audio, and documents in your object storage into searchable, timestamped results through one API.

[Search your own data](https://studio.mixpeek.com/namespaces/create?mode=managed&utm_source=homepage&utm_medium=diagram_detail&utm_campaign=mvs_onramp)

## Related diagrams

[

![The unstructured-data problem: the large majority of enterprise data is unstructured (video, images, audio, and documents) that keyword systems and relational databases cannot search by meaning until it is turned into embeddings and indexed. The raw files are stored but not answerable.](/diagrams/foundations/unstructured-data.webp)

99% of your data has no rows



](/diagrams/unstructured-data)[

![An embedding turns meaning into coordinates: a model reads 'dog', 'puppy', and 'invoice' and outputs vectors, so 'dog' and 'puppy' land near each other while 'invoice' lands far away. Text, images, audio clips, video frames, and faces all map into one shared coordinate space where distance measures difference in meaning.](/diagrams/foundations/embeddings.webp)

An embedding is meaning turned into coordinates



](/diagrams/embeddings)[

![Semantic search as nearest-neighbor lookup: embed the query into the same vector space as your content, measure distance to every indexed point, and return the closest top-K results with no keyword matching. Exact brute-force compares against everything and is accurate but slow, while approximate nearest-neighbor (ANN) indexes like HNSW and IVF check a smart fraction of the space and return 95-99% of true answers in milliseconds.](/diagrams/foundations/similarity-search.webp)

Search by meaning = nearest neighbors



](/diagrams/similarity-search)