About the author

Who writes this site

My name is pengchun. AITool.red is an independent project: I write the tools, the guides, the blog articles and the automated checks that sit behind them. There is no company behind the site, no editorial team, and no content agency, so when a page here is wrong, there is exactly one person responsible for fixing it.

I started the site because most single-purpose online tools are unpleasant to use: they bury the one thing you came for under advertising and interstitials, they ask you to sign up, or they quietly send what you typed to a server. The tools here are the opposite of that on purpose. Each one does a single job, runs entirely in your browser, and asks for nothing.

What I actually do here

• Build the tools. Plain HTML, CSS and JavaScript, one self-contained file per tool, no frameworks and no build step. That is a deliberate constraint: a plain file still works in five years, and you can read the whole implementation yourself.
• Write the guides. Every tool page carries a guide to the subject rather than instructions for the buttons: the rule or formula being applied, reference tables you could still use without the tool, the edge cases, and an honest note about when the tool is the wrong choice.
• Write the checks. This is the part most tool sites do not have. The numbers in a guide and the answers a tool gives are recomputed by a second, independent implementation, driven in a real browser, and compared byte for byte with what actually reached the server. The full process is described on the How we verify page.
• Keep it current. Rules change: time zone data is revised, scoring rules are adjusted, specifications are updated. Pages are revisited rather than published once and forgotten, and every tool page shows when it was last reviewed.

How the writing is done

I write the pages myself and I am accountable for what they say. Drafting is done with tooling assistance, and every page then gets a pass against primary sources before it goes live: specifications and RFCs for formats and encodings, the IANA time zone database for anything to do with clocks, government publications for dates that a government sets, and standard references for the rest.

Where a number in a guide can be recomputed, it is recomputed automatically before publishing, and the recomputation is kept so it runs again on every later change. Where a number cannot be recomputed, the guide says where it came from so you can check it yourself.

What I am accountable for

Three things, in plain terms. First, that the tools work and do what the page says they do. Second, that the guides are accurate and specific enough to be worth reading, rather than padded text wrapped around a button. Third, that when something is wrong it is corrected at the source and the check that should have caught it is added, so the same mistake cannot return unnoticed.

The verification process on this site grew out of real errors, not out of a template: each suite exists because something slipped through and needed to be pinned. That is also why the How we verify page lists what is not covered as carefully as what is.

Getting in touch

Bug reports, corrections and tool suggestions are all welcome and all read by me. Use the contact page. If you have found a factual error, please say which page and what the correct value is; a report like that usually becomes a fix plus a new check on the same day.