Developer tools
Embedding Storage Calculator
Estimate vector embedding storage from vector count, dimensions, precision, metadata, and index overhead locally in your browser.
Enter the number of vectors, the dimensions per vector, and the numeric precision. Optional metadata per vector covers IDs and payloads, and index overhead covers structures such as HNSW graphs. Storage uses 1 KB = 1024 bytes. The estimate runs locally in your browser; your values are not uploaded or stored.
Size a vector store before you load or index it.
Enter the number of vectors, the dimensions per vector, and the numeric precision. Optional metadata per vector covers IDs and payloads, and index overhead covers structures such as HNSW graphs. Storage uses 1 KB = 1024 bytes. Everything runs locally in your browser, so your values are not uploaded or stored.
Frequently Asked Questions
Everything you need to know about this tool, how it works, and privacy.
What does the embedding storage calculator estimate?
It estimates the raw vector bytes as vector count x dimensions x bytes per value for the chosen precision, then adds optional per-vector metadata and an index-overhead percentage for structures such as HNSW graphs. Storage uses 1 KB = 1024 bytes. For example, 1000000 vectors x 1536 dimensions in FP32 need about 5.722 GB before metadata and overhead.
Which precisions are supported?
FP32 uses 4 bytes per value, FP16 and BF16 use 2 bytes, INT8 uses 1 byte, and binary embeddings use 1 bit (0.125 bytes) per dimension. Quantized formats store less per value but can change recall quality, so confirm the tradeoff with your embedding model and vector database.
What should I enter for metadata and index overhead?
Metadata per vector covers IDs, payloads, and stored fields alongside each vector, in bytes. Index overhead is a percentage added on top for graph or inverted-index structures; HNSW indexes commonly add meaningful overhead that grows with graph settings, so use your measured or expected figure or leave both blank for raw vector bytes only.
Do my values leave my browser?
No. The estimate and the copy action run locally in your browser. CodeASystem does not upload or store the vector counts, dimensions, or storage figures you enter.