How FreeToolHub reviews tools and guides
This page explains what is checked before a workspace or guide is promoted, how browser-only claims are verified, and how corrections are handled.
A useful workflow comes before page count
A public tool must solve a distinct task or combine related steps into one coherent workspace. Overlapping single-purpose pages are merged or removed instead of being kept only for search coverage.
- The result must be usable, downloadable, or clearly actionable.
- Failure and unsupported-browser states must be explained.
- The page must include tool-specific limits and related guidance.
Functional checks use real inputs
File tools are checked with several sizes and formats. Permission-based tools are checked for allowed, denied, and unsupported states. Games are checked for controls, restart, saved progress, and responsive layout.
- Input, preview, processing, and export are checked separately.
- Large or invalid input must not produce a silent empty result.
- Desktop and mobile layouts are checked before release.
Guides document reproducible work
Guides are based on the current interface and include a stated verification scope. They describe limits and failure cases as well as the successful path.
- A review date and test coverage appear on every guide.
- Related tools are selected by the actual next step.
- Material changes are recorded in the public changelog.
Privacy claims follow the implementation
Files are described as local only when the related tool processes them in browser memory. Microphone, storage, translation, recording, and third-party runtime behavior are documented separately.
- No file upload is implied for browser-local tools.
- Permissions remain controlled by the browser.
- Object URLs, timers, and local state are cleaned up where the workflow requires it.
Advertising stays separate from controls
Advertising must not cover upload areas, permission prompts, game controls, result buttons, captions, overlays, or recording surfaces. Automatic ads remain disabled while the site is under review.
- Tool completion must not depend on an ad interaction.
- Ads are not placed inside exported or captured content.
- Policy, contact, and correction paths remain reachable without sign-in.