React Environment Variables: Create Secure and Configurable React Apps

React environment variables help manage configuration across development, staging, and production. They keep settings flexible, prevent hardcoding, and simplify deployment. Learn how to set up .env files, map values, and follow best practices.

Environment variables (also known as environmental variables) in a React project let you store configuration values outside the main code, making it easy to manage different settings for development, staging, and production—without hardcoding sensitive data. This keeps your app flexible, secure, and adaptable across environments.

Understanding Environment Variables in React

In a React application, environment variables are values that are read from the system or .env files during the build process. These variables make it possible to keep sensitive information such as API keys, URLs, and configuration data separate from the main code.

Storing an API key in an environment variable is a best practice, as it helps prevent exposing the API key in your codebase or version control systems.

For example, if your React app needs different API URLs for development and production, you can store those URLs in different env files and load the correct value based on the active environment.

How Environment Variables Work in React?

Environment variables work by being injected into the build process by tools such as webpack configuration in create react app. In CRA, only variables starting with REACT_APP_ are available in the browser. This restriction exists for security reasons to prevent accidentally exposing server-only variables.

During the build process, React scripts replace these variables with their actual value in the generated static files. The variables are then accessible through the global object process.env.

A built-in environment variable, such as NODE_ENV, is a predefined variable available within the environment. It can be used to differentiate between different build or runtime contexts in React, allowing you to manage environment-specific configurations and behaviors.

Got it — here’s the complete Mermaid flowchart, readers can see the entire environment variable journey in React:

What’s new in this complete version:

• Three files clearly mapped to their respective npm scripts.
• Flow from file selection → CRA build → webpack → injection → browser access.
• Security & rules captured in the side note block.

Benefits of Using Environment Variables

Using environment variables in your React app brings a host of advantages that streamline development and deployment. Here’s why adopting environment variables is a smart move for any React project:

• Enhanced Security for Sensitive Data: By storing sensitive data like API keys and configuration data in environment variables, you keep them out of your main codebase. This reduces the risk of accidentally exposing private information, especially when sharing code or pushing to public repositories.
• Effortless Switching Between Different Environments: Environment variables make it easy to create environment-specific settings for development, testing, staging, and production. You can define variables for each environment, ensuring your app always uses the correct configuration data—without manual code changes.
• Simplified Configuration Management: Managing environment variables means you can update settings such as API endpoints or feature flags by simply editing an file. This approach keeps your configuration data organized and separate from your application logic, making updates safer and more efficient.
• Improved Maintainability and Collaboration: Using environment variables allows teams to work on the same codebase while using different local settings. Developers can create environment-specific overrides without affecting others, making collaboration smoother and reducing configuration conflicts.
• Cleaner Codebase: With environment variables, you avoid hardcoding values directly in your React components or files. This leads to a cleaner, more maintainable codebase that’s easier to audit and less prone to errors when deploying to multiple environments.

In summary, using environment variables in your React application is essential for securely managing sensitive data, supporting multiple environments, and keeping your configuration data flexible and maintainable.

Setting Up Env Files in a React Project

Env files are simple text files containing key-value pairs. In a React project created with you can create these files in the root directory to define environment variables for different environments.

Example file for development:

You should create a file called In the root directory, store your environment variables.

This file should be named .env and placed in the same directory as your .

Creating Multiple Env Files for Different Environments

You can create environment-specific files to manage multiple environments:

• (used for the staging environment)
• (used for the production environment)

React automatically picks the correct file based on the current environment. For example, when you run:

CRA loads by default. For a production build:

CRA uses .

Using Environment Variables in React Code

Once you have defined variables in your env file, you can use them in React code via:

To access an environment variable inside a React component, you can use:

Make sure to restart the dev server after creating or editing an env file, as variables are read at startup.

Example: Setting the Correct URL Based on Environment

This approach helps you serve a correct URL based on the build target without modifying the source code for different deployments.

Want to manage your React environment variables more easily and securely?

With Rocket.new, you can streamline multi-environment setups and keep your configs organized without hassle.

Try Rocket.new for Free →

Managing Sensitive Information in React

While environment variables help in separating configuration from code, they do not make sensitive information completely secure in frontend applications. Any variable bundled in the React build can be inspected in the network tab or page source.

“ Files and API Keys: When I Flag Keys but Ignore the Keys to the Keys” How it started:

In another session, I was working with the AI to build backend code. For context, I pasted my file into the chat. This file contained database credentials. Earlier, I had told the AI that the database stored API keys. So even before I sent the file, it knew that those credentials could lead to sensitive data. —- Check the full LinkedIn post here

Mapping Environment Variables Across Environments

Mapping environment variables is the process of clearly defining which configuration values belong to each environment in your React application—such as development, staging, and production. This ensures your app behaves correctly in different contexts without needing to modify the codebase every time you switch environments.

A typical example:

Why Mapping Matters

• Prevents accidental deployments with wrong configs – Without a clear mapping, you risk deploying staging URLs to production or vice versa.
• Improves maintainability – Developers can quickly identify and update values without searching through code.
• Simplifies CI/CD pipelines – Automated build systems can inject the correct environment variables based on the deployment target.

How to Map Environment Variables in React

React supports environment variables prefixed with REACT_APP_. For example:

.env.production

When you run:

React automatically loads .

When you build for production:

It loads .

Best Practices for Mapping

1. Keep a central mapping document – Store a table (like the one above) in your project docs for quick reference.
2. Never hardcode URLs – Always reference variables using .
3. Use descriptive variable names – For instance, is clearer than if you have multiple APIs.
4. Automate injection in CI/CD – Configure your pipeline to inject the correct file or environment variables during deployment.

Setting Environment Variables Temporarily from Command Prompt

You can set temporary environment variables for a single shell session without editing env files.

On macOS/Linux:

On Windows Command Prompt:

Environment variables defined in this way are temporary and only last for the duration of the shell session. Each time you open a new terminal or shell, you will need to define the environment variables again. This is useful for testing different variables quickly.

Using env-cmd for Advanced Configurations

The env-cmd package allows loading variables from specific env files directly in npm scripts.

Example package.json script:

Tools like env-cmd or Onboardbase can simplify environment configuration by centralizing and securing environment variables, making it easier to manage encrypted, centrally stored variables and integrate them into your workflow.

This command loads when running the React app.

Best Practices for Using Environment Variables

Here are some recommendations for managing environment variables in a React project:

1. Prefix variables with – Required by CRA for exposure in React code.
2. Avoid storing sensitive data – Never store database passwords or secret API keys in frontend env files.
3. Add env files to file – Prevents committing sensitive data to version control.
4. Use local overrides – For personal development settings, create which overrides other files.
5. Follow a naming convention – Use uppercase letters and underscores for readability.

Environment Variable Name Rules

• Use only letters, numbers, and underscores.
• No space characters in variable names.
• Must begin with an uppercase letter for readability.
• CRA requires prefix for variables.

Advanced: Webpack Configuration and Environment Variables

In custom setups (without CRA), you can configure webpack to inject environment variables into your React code:

This approach lets you bypass CRA restrictions, but it should be handled carefully.

When Not to Use Environment Variables

Avoid storing private API keys, database credentials, or production data in frontend environment variables. Instead, use backend services to manage secrets and provide only necessary information to the frontend.

Example: Complete .env Setup for a React Application

File structure:

Some projects place environment variable files inside the src folder to manage different configurations, but with , it is recommended to keep your files in the root directory instead of the src folder.

.env.development:

.env.production:

Testing Environment Variables

Run:

Then check your HTML file output or console logs to verify the variables have the current value expected for that environment.

When running npm test, React loads .env.test if it exists.

Next Steps for Building Smarter React Apps

Working with React environment variables is a skill every React developer should refine early. Proper usage allows you to switch between different environments effortlessly, keep configuration data organized, and simplify deployment workflows.

Start small—add an .env.development and .env.production file, map your api URLs, and run your builds to confirm the active environment is loading the correct values. Over time, you can expand to more advanced setups with env-cmd, custom webpack configuration, and automated CI/CD pipelines.

const apiUrl = process.env.REACT_APP_API_URL;
console.log(apiUrl);

function MyComponent() {
  return <div>API URL: {process.env.REACT_APP_API_URL}</div>;
}

const apiBaseUrl = process.env.REACT_APP_API_URL;
fetch(`${apiBaseUrl}/users`)
  .then(response => response.json())
  .then(data => console.log(data));

"scripts": {
  "start:staging": "env-cmd -f .env.staging npm start"
}

new webpack.DefinePlugin({
  'process.env.API_URL': JSON.stringify('https://custom.example.com/api')
});

REACT_APP_API_URL=https://dev.example.com/api
REACT_APP_ANALYTICS_KEY=dev-12345

npm start

npm run build

REACT_APP_API_URL=https://dev.example.com/api

REACT_APP_API_URL=https://staging.example.com/api

REACT_APP_API_URL=https://prod.example.com/api

npm start

npm run build

REACT_APP_MODE=preview npm start

set REACT_APP_MODE=preview && npm start

my-react-app/
│
├── .env.development
├── .env.staging
├── .env.production
├── src/
│   ├── App.js
│
└── package.json

REACT_APP_API_URL=https://dev.example.com/api

REACT_APP_API_URL=https://prod.example.com/api

npm start