How to use the .env and connection string parser
1. Paste a .env file or connection URL
Drop dotenv key-value lines or a database connection string into the editor. The parser recognizes common separators and URL schemes.
2. Review variables in a table
Each key appears in a readable table with values masked when they look like secrets. Toggle reveal when you need to confirm a password or token locally.
3. Inspect connection string parts
Database URLs decompose into host, port, database name, user, and query parameters so misconfigured SSL or timeout flags are easier to spot.
4. Copy keys for configuration
Copy individual keys or reconstructed URLs into deployment manifests after verifying values without exposing secrets in screenshots.
Common use cases
Local development setup
Compare .env.example with your personal .env to find missing keys before starting services.
Database connection troubleshooting
Break apart PostgreSQL, MySQL, Redis, or MongoDB URLs to verify hostnames, ports, and SSL modes.
Security reviews
Confirm secrets are not accidentally committed in plaintext by parsing files locally with masking enabled.
Platform migrations
Translate Heroku-style DATABASE_URL values into split variables required by Kubernetes secrets.
Support handoffs
Redact sensitive values automatically while still showing which configuration keys exist for a failing deployment.
Frequently asked questions
- Which connection string formats are supported?
- Common RFC 3986 URLs for PostgreSQL, MySQL, Redis, MongoDB, and generic key-value .env syntax are supported.
- How does secret masking work?
- Keys containing words like password, secret, token, or key mask values by default. Use reveal toggles only on trusted devices.
- Are my secrets sent to drawflow.io?
- No. Parsing and masking happen entirely in your browser.
- Can I parse multiline certificates?
- Standard .env line pairs parse best. Multiline PEM blocks may need manual review depending on quoting in the source file.