Contact

Last updated: March 15, 2026

Primary contact channel

The direct support mailbox is dnlwjddnjs@gmail.com. For structured product reports, the preferred path is still the Feedback page because it keeps category, message, and trace context in one place.

This page is meant to serve searches such as imageee support, image converter bug report, pdf tool support, upload failed imageee, and metadata remover help. It exists to make support and correction paths crawlable and clear rather than sending users into generic policy pages.

Support and bug reports

Use the Feedback page as the primary contact channel for product questions, bug reports, and feature requests. Include the page URL, browser/version, device type, and clear reproduction steps. This information allows faster triage and reduces back-and-forth.

Feedback delivery and reference handling

The structured feedback form stores a submission reference before inbox delivery is attempted. If email routing is temporarily unavailable, the report is still recorded with that reference so it can be traced during support review. For urgent issues, include the reference ID when mailing dnlwjddnjs@gmail.com directly.

Policy and legal questions

For policy-related requests, submit through the same channel and select an appropriate category. If your request involves privacy, data handling, or legal compliance, include the affected URL, timestamp, and a concise description of the issue so the team can route it correctly.

Urgent service issues

If the service is unavailable or producing repeated processing failures, report one representative failing case first, including file type, approximate file size, and error message text. Avoid sending large batches of duplicate reports; one detailed report is more actionable than many minimal reports.

What to include in your message

Effective reports usually include: expected result, actual result, steps to reproduce, and whether the issue is consistent across multiple files. If the issue is format-specific (for example HEIC, AVIF, PDF split/merge), mention the exact workflow and target output format.

Response expectations

Response time depends on severity and workload. Critical production blockers are prioritized before general feature requests. Non-urgent suggestions are reviewed in roadmap cycles and may be bundled with related improvements.

What happens after you contact us

Reports are routed first by impact: repeatable processing failures, privacy issues, and delivery blockers ahead of cosmetic requests. When a message includes a reproducible case, the related workflow is checked against logs, limits, and current runtime behavior before any documentation or code change is made.

Minimum report template (recommended)

Include this compact template for faster handling: feature/page URL, source format and size, selected options, exact error text, expected result, actual result, and whether the issue reproduces across multiple files. This reduces follow-up questions and shortens triage time.

Sensitive data handling guidance for reports

Do not attach confidential originals unless absolutely required for debugging. Prefer redacted samples and minimal reproducible files. If a report involves personal, contractual, or regulated content, remove unnecessary identifiers from filenames and screenshots before submission. The team needs reproducibility signals, not full private datasets.

Escalation path for repeated production failures

If the same failure pattern blocks active operations, include a short incident summary: impact scope, start time, affected workflow, and temporary workaround status. This helps prioritize incident-class issues over isolated one-off errors and improves response quality for production users.