Convert structured data. A focused workspace that runs entirely in your browser.
{
"app": {
"name": "Northlane Tools",
"offline": true,
"version": 1
},
"features": [
"YAML to JSON",
"JSON to YAML"
]
}Small utilities for the jobs that interrupt real work: reshaping config, checking a pattern, getting a schedule right and catching mistakes in environment files. No account, and nothing leaves your browser.
Convert YAML to JSON or JSON to YAML in either direction, with readable two-space indentation and a clear message when the input can't be parsed.
Test a JavaScript regular expression against your own text with flags, see every match highlighted, and read a plain-English breakdown of the pattern.
Build a standard five-field cron expression (minute, hour, day of month, month, day of week) visually or by hand, starting from common presets, with the schedule explained in plain English.
Check an environment file for missing “=” signs, invalid or duplicate keys, empty values, unbalanced quotes and trailing whitespace, and get a warning when a value looks like a real secret.
No. Every tool runs in your browser tab. The YAML, JSON, patterns, schedules and .env values you enter are not sent to a server.
JavaScript regular expressions, the same engine your browser and Node.js use. Other flavours such as PCRE or Python differ in some features.
The standard five-field format used by Unix cron and most schedulers: minute, hour, day of month, month and day of week.
It flags values under keys such as API_KEY, SECRET, TOKEN or PASSWORD that look like real credentials rather than placeholders. It is a heuristic check, not a guarantee.
No. JSON has no comment syntax, so comments are dropped. Converting the JSON back to YAML gives you the same data without the original comments, blank lines or key styling.
The converter follows YAML 1.2, where only true and false are booleans. Older YAML 1.1 tools treated yes, no, on and off as booleans; here they stay as text, and when converting JSON to YAML such strings are quoted ('yes') so they stay text.
An unquoted date such as 2024-01-01 is a timestamp in YAML, and the JSON output writes it as a full ISO 8601 date-time in UTC. Put the date in quotes in your YAML if you want it kept as plain text.
Not in one go. The converter reads a single document, and a file with more than one shows an “expected a single document” error. Paste each document separately.
Aliases (*name) are expanded, so the JSON contains a full copy of the anchored value wherever it was referenced. Converting JSON to YAML never creates anchors; repeated values are written out in full.
The match list always scans the whole test string, so every match is shown and highlighted whether or not you add g. The other flags you enter, such as i, m or s, still change how the pattern matches.
It means every 5th value of that field. In the minute field, */5 runs at minutes 0, 5, 10 and so on up to 55 — twelve times an hour. In the hour field, */2 runs at 0:00, 2:00, 4:00 and so on.
Cron itself has no time zone in the expression — it runs in the time zone of the machine or service that executes it, which is often UTC on servers and cloud schedulers. The builder explains the fields but doesn't list upcoming run times; the cron expression generator linked above shows next runs in a chosen time zone.