Send feedback
Bug reports, UX issues, and feature requests are all welcome.
Messages are reviewed through the IMAGEEE support flow and can also be reached at support@imageee.net when direct contact is needed.
Each submission is stored with a reference ID for triage. If inbox delivery is temporarily unavailable, the form still records the report and shows the reference so the issue is not silently lost.
How feedback is handled
Reports are grouped by impact first: repeated processing failures, privacy concerns, and delivery blockers are reviewed ahead of cosmetic requests. Useful reports include the page URL, input type, selected options, exact error text, and one reproducible sample case.
If the same issue affects production work, include the affected workflow, when the problem started, and whether a workaround exists. This helps separate one-off confusion from incidents that need a code or documentation fix.
For abuse prevention, the form accepts normal product feedback but rejects automated floods, extremely large messages, and repeated submissions in a short time window. This keeps the support inbox usable, protects AWS processing cost, and avoids allowing one visitor to crowd out reports from other users.
Please send one detailed report per issue instead of many duplicate messages. A clear report with a reference URL, device, browser, file type, and visible error text is faster to investigate than a large burst of short messages, and it leaves a cleaner audit trail when the fix is deployed.
Feedback is also used as an operational signal. When multiple people report the same upload failure, preview bug, SEO issue, or mobile layout problem, the team compares the reports with server logs, request timing, and recent deployments before changing limits or behavior. That prevents one noisy report from causing a change that would make the tool worse for ordinary users.
If a file-processing problem looks urgent, send one representative case first and keep the original file available on your side. IMAGEEE processing storage is temporary, so support may need the format, approximate size, device source, selected options, and output expectation rather than the exact transient object that has already expired.