---
title: "Uncompressed vector embeddings"
description: "You can opt-out of using vector quantization to compress your vector data."
url: https://docs.weaviate.io/weaviate/configuration/compression/uncompressed
---

# Uncompressed vector embeddings

> [!NOTE]
>
> **Compression by Default**
>
> Starting with `v1.33`, you can set a default quantization for new collections using the [`DEFAULT_QUANTIZATION`](https://docs.weaviate.io/deploy/configuration/env-vars#DEFAULT_QUANTIZATION) environment variable. This variable is not set by default, meaning no quantization is applied unless you explicitly configure it. When set (e.g., to 8-bit [RQ quantization](https://docs.weaviate.io/weaviate/configuration/compression/rq-compression)), all newly created collections will use that quantization setting. Note that once set on a collection, quantization can't be disabled. Default quantization won't be applied to a collection if the index type isn't supported (for example PQ and SQ aren't supported for the flat index).

You can opt-out of using vector quantization to compress your vector data.

## Disable compression for new collection

When creating the collection, you can choose not to use quantization through the collection definition:

**Python**

```py
from weaviate.classes.config import Configure, Property, DataType

client.collections.create(
    name="MyCollection",
    vector_config=Configure.Vectors.text2vec_openai(
        quantizer=Configure.VectorIndex.Quantizer.none()
    ),
    properties=[
        Property(name="title", data_type=DataType.TEXT),
    ],
)
```

**JavaScript/TypeScript**

```ts
import weaviate, { configure } from '@weaviate/node';

await client.collections.create({
    name: "MyCollection",
    vectorizers: configure.vectors.text2VecOpenAI({
        quantizer: configure.vectorIndex.quantizer.none()
    }),
    properties: [
        { name: "title", dataType: weaviate.configure.dataType.TEXT },
    ],
})
```

**Java**

```java
client.collections.create("MyCollection",
    col -> col.vectorConfig(VectorConfig.text2vecTransformers(vc -> vc
        .quantization(Quantization.uncompressed())
    )).properties(Property.text("title")));
```

**C#**

```csharp
await client.Collections.Create(
    new CollectionCreateParams
    {
        Name = "MyCollection",
        Properties = [Property.Text("title")],
        VectorConfig = Configure.Vector(
            "default",
            v => v.Text2VecTransformers(),
            index: new VectorIndex.HNSW
            {
                Quantizer = new VectorIndex.Quantizers.None { },
            }
        ),
    }
);
```

## Additional considerations

### Multiple vector embeddings (named vectors)

Collections can have multiple [named vectors](https://docs.weaviate.io/weaviate/config-refs/collections#named-vectors). The vectors in a collection can have their own configurations, and compression must be enabled independently for each vector. Every vector is independent and can use [PQ](https://docs.weaviate.io/weaviate/configuration/compression/pq-compression), [BQ](https://docs.weaviate.io/weaviate/configuration/compression/bq-compression), [RQ](https://docs.weaviate.io/weaviate/configuration/compression/rq-compression), [SQ](https://docs.weaviate.io/weaviate/configuration/compression/sq-compression), or no compression.

### Multi-vector embeddings (ColBERT, ColPali, etc.)

> [!NOTE]
>
> **Added in `v1.30`**

Multi-vector embeddings (implemented through models like ColBERT, ColPali, or ColQwen) represent each object or query using multiple vectors instead of a single vector. On an `hnsw` index, multi-vectors support [PQ](https://docs.weaviate.io/weaviate/configuration/compression/pq-compression), [BQ](https://docs.weaviate.io/weaviate/configuration/compression/bq-compression), [RQ](https://docs.weaviate.io/weaviate/configuration/compression/rq-compression), [SQ](https://docs.weaviate.io/weaviate/configuration/compression/sq-compression), or no compression. On an `hfresh` index (from `v1.40`), the MUVERA encoding is always compressed with 1-bit RQ.

During the initial search phase, compressed vectors are used for efficiency. However, when computing the `MaxSim` operation, uncompressed vectors are utilized to ensure more precise similarity calculations. This approach balances the benefits of compression for search efficiency with the accuracy of uncompressed vectors during final scoring.

> [!NOTE]
>
> **Multi-vector performance**
>
> RQ supports multi-vector embeddings. On an `hnsw` index, each token vector is rounded up to a multiple of 64 dimensions, which may result in less than 4x compression for very short vectors. This is a technical limitation that may be addressed in future versions.

## Further resources

- [Starter guides: Compression](https://docs.weaviate.io/weaviate/starter-guides/managing-resources/compression)
- [Reference: Vector index](https://docs.weaviate.io/weaviate/config-refs/indexing/vector-index)
- [Concepts: Vector quantization](https://docs.weaviate.io/weaviate/concepts/vector-quantization)
- [Concepts: Vector index](https://docs.weaviate.io/weaviate/concepts/vector-index)
