> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/self-managed-enterprise-edition/use-self-managed-enterprise-edition/advanced-configuration/configure-image-digest.md).

# Configure Image Digest

{% hint style="info" %}
**NOTE:**

This feature is available from Harness Helm Chart version 0.27.0 By default, Harness Helm Chart uses image tags for all services. If an image digest is not available, the system automatically falls back to using image tags.
{% endhint %}

This topic describes how to configure Harness services to use image digests instead of tags for container images.

#### Overview <a href="#overview" id="overview"></a>

Container image digests are cryptographic hashes of an image's content, providing an immutable identifier for a specific version of an image. Unlike tags which can be moved or overwritten, digests ensure you're always deploying the exact same image content.

#### Configure Image Digest for all services <a href="#configure-image-digest-for-all-services" id="configure-image-digest-for-all-services"></a>

You can enable image digest for all services using the global override of helm chart.

```yaml
global:
  preferDigest: true
```

#### Important Note <a href="#important-note" id="important-note"></a>

This feature will only work if default registry used is same as in helm charts. Mismatched digests will cause pull failures when `preferDigest: true` is enabled.