Popular frameworks have built-in "loading orders." For instance, in , the hierarchy looks like this: .env.local (Highest priority) .env.development / .env.production .env (Lowest priority)
If you’ve ever accidentally pushed an API key to GitHub or struggled with different database URLs between your laptop and your teammate’s, .env.local is the solution you’re looking for. .env.local
While it looks like a simple text file, it plays a critical role in keeping your application secure and your development workflow smooth. Popular frameworks have built-in "loading orders
Add your variables using the KEY=VALUE syntax. Note: If you are using a frontend framework, you often need a prefix (like NEXT_PUBLIC_ or VITE_ ) to expose these variables to the browser. Note: If you are using a frontend framework,
# SENSITIVE: Keep this private! STRIPE_SECRET_KEY=sk_test_51Mz... # PUBLIC: Accessible by the browser NEXT_PUBLIC_ANALYTICS_ID=UA-123456789 Use code with caution.
You might be using a local Docker database, while your teammate prefers a cloud-based dev database. By using .env.local , you can both have different DATABASE_URL values without conflicting with each other’s code.