Quality and safety practices

We develop and review each tool to make its behavior match its documentation and to avoid transmitting input unnecessarily. This page explains our publication checks and the limits of what we can guarantee.

Checks before publication

Code linting and TypeScript type checking
Unit tests for processing rules and boundary cases
End-to-end checks for core Japanese and English flows on desktop and mobile
Production builds and checks for internal links, canonical URLs, hreflang, and the sitemap
Privacy tests that reject analytics or error-monitoring payloads containing inputs, passwords, file names, or image information

What local processing means

Unless a tool page says otherwise, tool input and conversion run in your browser. Loading the site, consented analytics, and error monitoring still involve network requests, so local processing does not mean that the page makes no network requests at all.

Supported scope and limitations

Formats, size limits, pixel limits, and conversion rules differ by tool. Review the notes on each tool page. Results can differ by browser, operating system, and input, so independently verify output used for important work.

Defects and corrections

When we confirm a defect or inaccurate explanation, we investigate its scope and update the implementation, tests, and documentation together. Reports should include the browser, operating system, and reproduction steps. Do not send passwords, secrets, personal information, or private files.