Contact

Tell us what needs fixing.

FileGizmo has no account system or support form that stores your message. Product feedback and reproducible bug reports are handled through the project’s GitHub issue tracker.

Report a bug or request a tool

Open a FileGizmo issue on GitHub. Before posting, check whether the same problem or request already exists.

A useful report includes the tool name, browser and operating system, the steps you took, what you expected, and what happened instead. If possible, use a harmless sample file that contains no private information.

Never attach a sensitive originalGitHub issues are public. Do not post personal documents, API keys, identity records, private images, or confidential business data. Describe the structure of the file or create a safe reproduction instead.

Security reports

If a problem could expose another person’s information or create an active security risk, do not publish exploit details or real files. Open a minimal issue asking for a private reporting channel, without including the sensitive details. The maintainer can then arrange an appropriate private handoff.

What to expect

FileGizmo is independently maintained and does not promise a fixed response time. Clear, reproducible failures receive priority over broad feature requests. A request may be declined when it would require uploading files, weaken the privacy model, or add disproportionate complexity.

Before contacting us

Try the file again in a current version of Chrome, Edge, Firefox, or Safari.
Confirm the file opens normally in another trusted application.
Read the tool’s limits and error message; encrypted or malformed files may need preparation first.
Check the changelog for a recent fix.