How Our Tools Work
How tools run in the browser
Most FunnyTools tools are static browser tools. After you open a tool page, form inputs, buttons, formulas, and result displays usually run inside your current browser tab, with no server round-trip required to get a result.
Local-processing tools include word counters, case converters, text cleanup tools, random pickers, timers, salary and loan calculators, image compression and conversion, PDF merge and split tools, statistical tests and percentile calculators, sketching, and flowchart tools. These inputs are not actively uploaded to FunnyTools servers.
How a tool gets picked, and what stays out of scope
Whether a new tool is worth building comes down to three things: can it run entirely in the browser, is it a specific task enough people run into repeatedly, and does it avoid needing to store sensitive user data long-term. Tools like random grouping, unit conversion, and grade percentile calculators fit all three and tend to get prioritized.
Some categories are intentionally out of scope for now: anything that requires account creation to use, anything that needs a persistent server-side user database, or anything that needs heavy server-side computation (large-scale machine learning inference, for example). Those needs go beyond a static, browser-first site and don't fit the local-processing priority described above.
Images, PDFs, and local storage
Image and PDF tools read files in your browser and generate downloadable results locally. The file content is processed in your device's memory during the operation, and you download the finished result directly when it's done.
Some tools may use localStorage for preferences such as timer lengths or interface options. That data is stored in your browser only — it doesn't sync to other devices or to a FunnyTools server, and it can be removed at any time by clearing your browser data.
Calculation results and their formal-use limits
Calculation results have limits. Salary, overtime, loans, compound interest, inflation, business days, GPA, and grade average tools usually rely on simplified formulas or the values you enter. They do not cover every law, company policy, bank condition, school rule, or rounding difference that might apply to your specific situation.
Results are reference-only because real-world outcomes can depend on updated regulations, regional differences, contract terms, actual rates, personal circumstances, source data, or professional judgment. For money, legal, medical, tax, or formal-rights decisions, rely on official documents or qualified advice instead of a calculator result.
Browsers and devices have their own limits. Processing a large PDF or a high-resolution image is slower on lower-powered devices or when memory is limited, and older browsers may not support some of the file-processing features these tools rely on. If a tool seems unresponsive, updating your browser or trying a newer device is a reasonable first step.
Bug reports and tool suggestions
To report an error, email btcson66@gmail.com or open an issue at https://github.com/btcson66-rgb/funnytools-win/issues with the tool page URL, the steps you took, your input conditions, the expected result, the actual result, and your device and browser.
To suggest a new tool, reach out the same way. Describe the problem it should solve, what inputs it needs, what output it should produce, and the use case you have in mind — specific suggestions are easier to prioritize than general requests.
Tools are kept intentionally single-purpose rather than bundled into one large multi-step app. That keeps each page focused and easy to scan, and it means a fix to one tool is unlikely to introduce a regression in an unrelated one.
If you're not sure whether a task can be done locally in the browser, the safest test is simply trying the relevant tool with a small, non-sensitive example first — if the result looks right, the same approach will generally work for your real file or numbers.