Contact guidance

How to send a useful tool report

A clear report helps us determine whether a problem comes from the tool, browser, source image, selected settings or expected workflow. Start with the exact tool name and page address. Describe the action taken, options selected, result received and result expected. If the issue happens consistently, list the steps in order so the same path can be tested.

Include the device, operating system and browser when they may affect the result. Image processing can behave differently when a browser lacks format support, a device has limited memory or an extension blocks a required feature. A small, non-sensitive sample is useful, but never send an original file containing private or protected information.

Broken pages, links and unexpected output

If a page displays an error, redirects incorrectly or opens the wrong tool, include the exact address and tell us where the link was clicked. Before reporting, refresh the page and try a private browser window if practical. If the issue began after a WordPress update, clear relevant site and browser caches, then test again.

For an image output issue, include the source format, approximate dimensions, chosen settings and output format. Describe the visible problem precisely: incorrect crop, missing transparency, color shift, blur, jagged edges, download failure or unexpected file size. Some outcomes reflect source limitations, but we still welcome reports when the interface does not explain those limits clearly.

Content corrections

We welcome specific corrections when an article contains an inaccurate statement, outdated recommendation, broken table, duplicated section or confusing example. Include the article title, link and heading. Quote only the short sentence needed to locate the issue, then explain the correction and why it is more accurate.

For browser features, format specifications or accessibility standards, include a reliable primary source where possible. Requests are reviewed for relevance, accuracy and clarity. Accepted changes may be edited to match the article style, while unrelated content remains unchanged unless the correction identifies a wider issue.

Accessibility feedback

Accessibility reports can cover keyboard traps, missing focus indicators, low contrast, unclear labels, screen-reader announcements, zoom problems, touch target sizes, motion or dark-mode readability. Describe the device, browser, assistive technology and settings used, then identify the page and the action you were trying to complete.

If you found a workaround, include it. That can help identify the conditions that cause the barrier without treating the workaround as a permanent solution. Screenshots can be useful, but remove personal names, email addresses, browser tabs and confidential information first.

Privacy and sensitive information

Never send passwords, payment details, identification numbers, medical information, confidential client files, protected records or access credentials. We generally need a description, not the original sensitive image. Create a substitute file or sanitized screenshot that demonstrates the same behavior whenever possible.

Check filenames, visible backgrounds and metadata before sharing an example. Do not submit a file unless you own it or have permission to use it for support. The form is for genuine assistance and feedback, not for transferring confidential records.

Feature and partnership suggestions

Feature requests are strongest when they describe a recurring problem, the current workflow and the outcome needed. Examples include a missing format, aspect-ratio preset, clearer preview, batch behavior, accessibility improvement or validation rule. Requests are evaluated against privacy, security, performance, compatibility and usefulness.

Business messages should identify the organization, proposed relationship and benefit for ImageForge visitors. Generic bulk outreach, misleading offers, undisclosed paid-link requests and proposals that conflict with visitor privacy may not receive a response.

WordPress installation questions

For installation problems, include the theme version, WordPress version, PHP version if known, hosting environment and exact error. Clarify whether it happened during ZIP upload, activation, starter-content import or page viewing. Mention whether permalinks were refreshed, caches cleared and Reading settings checked.

If the site looks outdated after an update, identify any caching plugin, optimization service or content delivery network in use. Never send hosting passwords, dashboard credentials, database exports or secret keys through the form.

Copyright, security and response expectations

Rights concerns should identify the protected work and the exact page or asset involved, and formal notices should follow the website's DMCA process. Security reports should explain the affected feature, impact and safe reproduction steps without accessing other users' data, disrupting the service or publishing sensitive details.

Messages are reviewed according to clarity, impact and reproducibility. Broken tools, security concerns, widespread accessibility barriers and factual corrections may receive higher priority than general suggestions. Not every request can be implemented immediately. One complete, descriptive message is more useful than repeated reports without a page, tool or expected result.

Our commitment to useful feedback

We appreciate respectful feedback that helps make ImageForge more accurate, accessible, secure and useful. Before submitting, refresh the page, clear relevant caches and confirm the issue still occurs. For tool errors, include a short non-sensitive example; for corrections, identify the article and heading.

These details let us investigate the specific problem while protecting unrelated features and visitor privacy. The contact form should not be used for confidential records, unsolicited bulk promotions or requests that conflict with responsible publishing standards.