Contact

one address for the whole network · [email protected]

Reporting a bug

A useful report has three parts: (1) the URL of the tool, (2) what you expected versus what happened, and (3) a sample file that triggers it. The third is worth more than the other two together — without a reproducer I am guessing, and browser-side bugs are usually specific to one awkward file.

Because nothing is uploaded, I have no copy of what you were working on and no logs of it. If you attach a file, please make sure you are allowed to send it, and redact or synthesise anything sensitive first — the privacy policy covers what happens in your browser, not what you choose to email me.

Requesting a tool

Search all 809 tools first; a surprising number of requests already exist under a different name. If it genuinely is not there, say what you were trying to do rather than how you imagine the tool should work — the underlying task usually suggests a better tool than the requested one.

Corrections to this index

This page is generated from each site's own catalogue, so a wrong name or count here usually means something is wrong at the source. Point at the row and I will fix the origin, not the symptom.

Links, mirrors and reuse

Linking to any of these tools from documentation, a README, a course or a blog post is welcome, no permission needed. If you maintain a list of developer tools and want the catalogue as data rather than as links, /catalog.json on this domain is the whole index in one file — 809 entries with names, categories and URLs. Take it rather than scraping the pages.

What I cannot help with

• Recovering a file. There is no copy anywhere — closing the tab really does end it.
• Bulk or automated processing. These are hand-driven tools. Two kits have CLI companions on GitHub if you need a pipeline.
• Guaranteed turnaround. One person, evenings and weekends. Real bugs get priority over new tools.

— S., [email protected]