Report an Issue
If the troubleshooting guides do not resolve the issue, contact Imgwire support with enough detail to reproduce or investigate the problem.
You can email support@imgwire.dev, or visit imgwire.dev/support. The support page includes the link to join the Imgwire Discord server, where you can get help from moderators and other developers.
What to include
Include the smallest set of details that clearly identifies the failing workflow:
| Detail | Why it helps |
|---|---|
| Organization and Environment | Helps support locate the correct scoped resources |
| Image ID or CDN URL | Identifies the affected image or delivery variant |
| API endpoint and HTTP method | Shows which Resource API workflow failed |
| HTTP status and response body | Shows the exact Imgwire error and error_type |
| Time of failure and time zone | Helps correlate logs and metrics |
| SDK or CLI package and version | Helps reproduce client-side behavior |
| Browser and origin | Helps debug CORS and frontend upload issues |
| File type, size, and dimensions | Helps debug upload validation and pixel limits |
| Transformation parameters | Helps debug CDN delivery and image output |
| Custom domain hostname | Helps debug DNS, certificate, and routing issues |
Do not send Server API Keys, Client Keys, upload tokens, session cookies, or payment card numbers in support messages.
Good report template
Subject: Imgwire upload issue in production
Organization:
Environment:
Dashboard email:
Issue:
Expected behavior:
Actual behavior:
When it happened:
Affected image ID or CDN URL:
API endpoint or SDK method:
HTTP status and response body:
Client details:
- SDK/CLI package and version:
- Browser or runtime:
- Browser Origin header, if relevant:
File or transformation details:
- File name:
- MIME type:
- File size:
- Pixel dimensions:
- Transformation URL or parameters:
Steps to reproduce:
1.
2.
3.
Upload issue reports
For upload issues, include:
- Whether the flow used a Client Key or Server API Key.
- Whether signed uploads are required.
- Whether the upload token endpoint succeeded.
- The
standard_uploadresponse, excluding secrets. - Whether the bytes were uploaded to the returned
upload_url. - File MIME type, file size, and pixel dimensions.
- The browser
Originheader if it is a browser upload.
Transformation and delivery reports
For transformation or CDN delivery issues, include:
- The source image ID.
- The exact CDN URL that failed.
- The expected output dimensions, format, and crop behavior.
- The response status and response headers if available.
- The browser or tool used to request the URL.
- The request
Acceptheader ifformat=autois involved. - Whether the default Imgwire CDN URL works when a custom domain fails.
Custom domain reports
For custom domain issues, include:
- Hostname, such as
cdn.example.com. statusandcertificate_status.- The returned
cname_record,cname_value,dcv_cname_record, anddcv_cname_value. - Whether
POST /api/v1/custom_domain/test_connectionchanges the status. - A screenshot or copy of the relevant DNS records from your DNS provider, excluding unrelated private records.
Billing or account reports
For billing or account issues, include:
- Organization name.
- Dashboard email address.
- Plan shown in the dashboard.
- Invoice number or billing period, if relevant.
- Error message or
PaymentRequiredErrorresponse, if available. - Whether the issue affects uploads, transformations, custom domains, team members, or dashboard access.
Related pages
- Uploading Images
- Transformations
- Custom Domains
- Billing and Plans
- Account Access and Login
- Production Issues and System Status
Last updated at: May 8, 2026