# Build logs now redact Sensitive Environment Variable values

DevFeed: [Build logs now redact Sensitive Environment Variable values](<https://devfeed.tech/articles/build-logs-now-redact-sensitive-environment-variable-values-826.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/build-logs-now-redact-sensitive-environment-variable-values>)

Author: Andrew Healey

Published: 2026-07-09T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [deployment](<https://devfeed.tech/tags/deployment.md>), [logs](<https://devfeed.tech/tags/logs.md>), [security](<https://devfeed.tech/tags/security.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel now redacts sensitive environment variable values of 32 characters or longer from deployment build logs. The Build Logs view indicates when redaction occurs, while the Activity Log records the variable key, project, and deployment without exposing the value.

## Source excerpt

When an Environment Variable is marked Sensitive and has a value 32 characters or longer, Vercel now replaces it with [REDACTED] in the deployment's build logs. The Build Logs view also indicates when redaction happened, giving teams visibility into why output was masked without ever exposing the underlying value. When a value is redacted, Vercel logs the Environment Variable key, project, and deployment in the Activity Log, but never the value. Vercel also redacts selected system Environment Variables used for deployment security. Learn more about Sensitive Environment Variables. Read more