ENV Validator & Cron Explainer
Validate .env files against a template and decode cron expressions into plain English with a calendar preview.
Learn more Browser-first developer tools
Catch missing environment variables and understand cron schedules before they break local or production workflows.
What to expectIn the ENV tab, compare .env values against a template. In the Cron tab, decode an expression into plain English and preview upcoming runs.
Good to knowThis is especially useful during onboarding, deploy setup, and debugging scheduled jobs.
How it works
- In the ENV tab, paste your
.envcontents and optional.env.exampletemplate. - Review the differences to see missing, extra, or undocumented variables, or switch to the Cron tab to paste a schedule expression.
- Use the results panels to understand issues or upcoming run times before updating your configuration files.
All validation happens locally in your browser. Environment variables and cron strings are never transmitted to any server.
Paste your files
Compare your real .env against .env.example to catch missing or undocumented variables.
Results
Paste your .env to see missing, undocumented, duplicate variables and security warnings.
Frequently Asked Questions
What is the difference between .env and .env.example?
.env contains your real secret values and should never be committed, while .env.example documents which variables your app expects with placeholder values and is safe to commit. The validator compares the two to highlight missing, extra, or undocumented variables before they cause runtime bugs.
How do I read a cron expression like "0 9 * * 1"?
The expression 0 9 * * 1 means "at 9:00 AM every Monday." The Cron tab parses each field, shows a plain-English explanation, and lists the next few scheduled run times so you can confirm the schedule matches your intent.
Does this tool store my .env file contents?
No. Your environment file contents are processed only in your browser; API keys, secrets, and other sensitive values are never transmitted to any server or third-party API. Closing or refreshing the page clears them from memory.
Can I use this validator in a CI pipeline?
The UI is for interactive checks, but it mirrors a simple rule set you can implement in CI: ensure every variable in .env.example has a value in your runtime environment and flag unexpected keys. You can prototype comparisons here before wiring them into your build scripts.
Will this tool tell me if I accidentally committed secrets to git?
The ENV validator focuses on comparing variable names and values between files; it does not scan your git history or remote branches. You should still use dedicated secret-scanning tools for repositories while using this UI to prevent configuration drift.
How does timezone selection affect cron explanations?
When you pick a timezone, the next run times are calculated relative to that zone so you can see exactly when a job executes in production. This is especially helpful when servers run in UTC but your team plans schedules in a local timezone.
How to use this tool
ENV tab: paste your .env on the left and .env.example below to find missing or undocumented variables. Cron tab: paste any cron expression to see exactly when it runs, with the next 5 scheduled dates.