DEVHOLSTER

All tools

Every tool on devholster on one page, grouped by category. 73 of them so far, all running in your browser tab, all free and without an account. If you already know what you are looking for, the search below beats scrolling.

73 tools.
7 categories.

Nothing you paste is uploaded, and once a tool has loaded it keeps working offline. Free, no signup.

.yaml JSON to YAML Turn JSON into clean YAML for configs and pipelines. .json YAML to JSON Anchors and merge keys resolved on the way back to JSON. .toml JSON to TOML TOML configs for Cargo, pyproject and friends. .json TOML to JSON Cargo.toml or pyproject.toml as plain JSON. .xml JSON to XML JSON as XML, with the root element and attributes you pick. .json XML to JSON Feeds, SOAP and sitemaps parsed into JSON, attributes included. .xml YAML to XML YAML configs converted straight through to XML. .yaml XML to YAML Read an XML document as YAML, attributes preserved. .toml YAML to TOML Config migration: anchors resolved, nulls handled explicitly. .yaml TOML to YAML [[Sections]] become lists, dates stay real timestamps. .toml XML to TOML Legacy XML configs as TOML tables, attributes kept. .xml TOML to XML TOML into well-formed XML, dates as ISO 8601. .csv XML to CSV The repeated element becomes rows, attributes become columns. .xml CSV to XML Rows as elements, with root and row names you pick. .csv JSON to CSV Flatten nested API responses into Excel-ready CSV. .json CSV to JSON Spreadsheet exports become typed JSON arrays. .csv YAML to CSV The record list found anywhere in the tree, as clean rows. .yaml CSV to YAML Rows into a YAML list, ambiguous values safely quoted. .toml CSV to TOML Each row a [[table]], empty cells handled cleanly. .csv TOML to CSV [[Tables]] as spreadsheet rows, dates as ISO 8601. .tsv CSV to TSV Swap commas for tabs, quoting handled properly. .csv TSV to CSV Tab-separated exports back to RFC 4180 CSV. .md CSV to Markdown Table Paste a CSV, get an aligned Markdown table for the README. .csv Markdown Table to CSV Pull a Markdown table back out into CSV. .html CSV to HTML Table A ready-to-paste HTML table with thead and escaping. .sql CSV to SQL INSERT Rows become INSERT statements for your dialect. .xlsx CSV to Excel A real workbook: leading zeros, long IDs and umlauts survive. .csv Excel to CSV Any sheet of an .xlsx as clean UTF-8 CSV, dates as ISO. .csv Change CSV Delimiter Semicolon to comma and back, with the quoting redone.
Your code stays on your machine.
Runs in your browser

The parsers ship with the page, so a tool keeps working after you go offline.

Instant, as you type

Every tool runs the moment you type. No run button, no waiting, nothing to install.

Free forever, no signup

No account, no paywall, no trial that expires. All 70+ tools, free for everyone.

Using web tools for real work

How can I tell whether an online tool uploads what I paste?

Open the network tab of your browser devtools, clear it, then use the tool and watch whether a request goes out while you type or when you press the button. A page that does the work locally makes no request at all beyond loading its own scripts. The stronger version of the test is to load the page, disconnect from the network and try again: anything that still works cannot have sent your input anywhere. A privacy policy is a promise, the network tab is evidence.

Is pasting company code into a web tool against policy?

In many organisations, yes, and the policy usually names the category rather than the site: source code, customer data and credentials must not be sent to third-party services without review. That is aimed at anything that transmits the input, which covers most online tools and every AI assistant, but not a page that computes in your own browser. Since the distinction is invisible from the outside, the defensible answer to a security review is a network capture, not a claim from the homepage.

When is a browser tool the wrong choice compared with a CLI?

When the file is large, when the job has to repeat, or when it has to run in CI. A browser tab holds the whole input in memory, so a multi-hundred-megabyte file belongs in a streaming command line tool, and anything that must run on every commit belongs in a script where it is versioned and reviewable. Web tools win for the one-off: a payload from a ticket, a config someone mailed you, a token you need decoded now, with nothing to install.