Best way to reach the project
The public DailyWebTools project repository is currently the clearest contact channel. For bug reports, corrections, accessibility issues, and tool suggestions, open an issue at github.com/garry-lin/dailywebtools/issues. A dedicated branded support email can be added after a production domain is connected.
Please do not paste private passwords, API keys, secret tokens, personal documents, or confidential business data into a public issue. If a bug involves sensitive data, describe the problem with a safe sample instead.
What to include in a bug report
| Tool or page | For example: JSON Formatter, Image Compressor, Word Counter, Discount Calculator, or the tool directory. |
|---|---|
| Device and browser | For example: iPhone Safari, Android Chrome, Windows Chrome, macOS Safari, or desktop Firefox. |
| Expected result | Explain what you expected the tool to calculate, convert, generate, resize, format, or display. |
| Actual result | Describe what happened instead, including any visible error message or incorrect output. |
| Steps to reproduce | List the actions that caused the problem so it can be tested again with safe sample data. |
Tool suggestions we welcome
Useful suggestions include everyday calculators, writing utilities, image helpers, date and time tools, developer tools, generators, converters, study tools, and accessibility improvements. DailyWebTools prioritizes tools that can run safely in the browser, solve a clear recurring task, and help a broad global audience.
Privacy and correction requests
For privacy questions, outdated page copy, broken links, accessibility problems, or incorrect examples, include the exact URL and the correction you are requesting. DailyWebTools does not require user accounts for core tool use, and many tools run locally in the browser, but public website issues can still be reported through the repository.
Before opening an issue
Check whether the problem happens after refreshing the page and whether it appears in another browser. For image tools, try a small non-sensitive sample image. For developer tools, replace private tokens, API responses, or user records with safe dummy data before sharing examples.
If the request is a new tool idea, describe the exact job the tool should do, the input fields visitors need, the output they expect, and any privacy or accuracy warnings that should appear on the page. Clear requests help prioritize tools that are useful for many visitors.
Response expectations
DailyWebTools is a free utility site, so support focuses on site reliability, corrections, privacy questions, accessibility, and practical tool improvements. The site cannot provide professional legal, medical, financial, tax, security, or engineering advice based on tool results.