Dev Kit looks and works like a code editor, with the tools you reach for every day built in. Open a file on the left, edit it in the middle, run a tool beside it and read the result. Everything happens in your browser, so private data, logs and tokens stay on your device.
How it works
Paste text, open a file or drop one anywhere on the window. The editor tells you what it is: JSON, YAML, CSV, TSV, XML, TOML, .env, a JWT, a cURL command, SQL, logs or plain text. Every tool reads from the same input, so you never copy data from one tool into the next. Open input B when you need a second version to compare, a JSON Schema to check against, or a second table to join.
Each tool has Use as input and Send to B buttons. Convert a CSV to JSON, use the result as the input, query it with jq, then send the matches to input B and compare them with the original. Every change to the input can be undone.
The tools
- JSON formats, minifies and validates, shows a collapsible tree, runs JSONPath and jq filters, checks the data against a JSON Schema in input B, and writes TypeScript, Zod, Go or Python types. YAML, CSV, XML and TOML are read as data too.
- Convert turns JSON, YAML, TOML, XML, CSV, TSV and .env into one another.
- SQL runs real SQLite. The input becomes a table called
dataand input B becomesdata_b, so you can join them. Open a SQLite database file and its tables are ready to query too. - Regex highlights every match, lists the capture groups, previews a replacement and explains the pattern piece by piece.
- Diff compares the input with input B, or with the result of any other tool.
- Encode and decode handles Base64, URL encoding, HTML entities, hex, MD5 and SHA hashes, and decodes JWTs with readable dates. Hash a file gives the MD5 and SHA checksums of any file, read on this device.
- cURL and requests turns a cURL command into fetch, axios, Python requests, Go, PHP or PowerShell code. Build a request starts from a form instead: method, address, query, headers, sign-in and body become a cURL command or code you can copy. No request is ever sent.
- Format code formats or minifies JavaScript, CSS, HTML, XML, SQL, JSON and YAML, picks the language for you, and points to the line when the input is broken.
- Generate and convert makes UUIDs, passwords and placeholder text, and reads the input as a Unix timestamp or date, a cron schedule with its next runs, a colour, a number in any base, or a value with a unit such as
24px,2048 KiBor90min.
The inspector, the panel and the terminal
The inspector on the right shows the current data as a tree, a table or a list of fields with their types. The panel along the bottom has three tabs. Output lists what ran. Problems lists parse errors, schema errors and likely secrets, and clicking one jumps to its line. Terminal runs jq, json, grep, head, wc, base64 and more on the input, with pipes, and opens the full Snowkit Shell for anything else.
A quiet guard for secrets
When the input looks like it holds an API key, a private key, a token or a password, a calm note says so and offers to mask it with one click. Nothing is sent anywhere either way, and Undo brings the original back.
Your session is saved
The inputs, the tools you have open and their settings are kept in this browser, and each session is saved to your Library so you can come back to it. Very large inputs, over about two million characters, are not kept, though the settings still are. Export the whole session as a JSON file to move it to another computer, and import it there. Start over clears the editor and begins a fresh session, and the previous one stays in your Library. Save the input as a snippet to keep a query, a pattern or a command you use often: snippets stay in the sidebar on this device, with a search box once there are a few. Tokens and passwords typed into Build a request are never kept. Signed in, the Snowkit file button at the top right also offers Share privately, which sends your work as a private link that opens right where you left off.
Keyboard shortcuts
- Ctrl K or Ctrl Shift P opens the command list, where every action can be found by typing
- Ctrl Enter runs the tool you are working in
- Alt or Ctrl with 1 to 9 switch tools
- Ctrl O opens a file and Ctrl S downloads the result
- Ctrl J shows or hides the bottom panel
- Ctrl Z and Ctrl Shift Z undo and redo changes to the input
Privacy
All of the work happens in your browser. Your data, tokens and queries are never uploaded, and the cURL tool only writes code, it never makes the request. The saved session lives in this browser and your Library. It leaves this device only if you choose Share privately, or with Snowkit Cloud on, encrypted on your device before it syncs.
Questions
How large can the input be?
Files up to 25 MB open, and several megabytes work well on a computer. Tools only run while they are on screen, patterns run in the background with a time limit, and long highlights and tables stop at a sensible size, so the editor stays responsive.
Is the JWT signature checked?
No. The header and payload are decoded and the dates are explained, but checking a signature needs the secret or public key. Never paste a production secret into a website you do not control.
Which SQL can I use?
Full SQLite: joins, grouping, window functions, common table expressions and JSON functions. Nested JSON objects become columns such as customer_name.
Which jq filters work?
The everyday ones: paths, pipes, select, map, keys, length, add, object and array construction, comparisons and many built-in functions. A filter that is not supported says so instead of guessing.