Use one account and a consistent result format for image checks, conversions and calculations. Hosted processing is billed separately from the free local web tools.
Choose an operation
Image operations use a private uploaded file. Numerical operations accept the quantities needed for their calculation. AI reports retain execution state and source details rather than reducing missing signals and failures to the same boolean.
| Group | Operation | Task | Input overview |
|---|---|---|---|
| Calculations | pixels-to-inches | Pixels to inches | width, height, ppi |
| Calculations | inches-to-pixels | Inches to pixels | width, height, ppi |
| Calculations | pixels-to-cm | Pixels to centimetres | width, height, ppi |
| Calculations | cm-to-pixels | Centimetres to pixels | width, height, ppi |
| Calculations | pixels-to-mm | Pixels to millimetres | width, height, ppi |
| Calculations | mm-to-pixels | Millimetres to pixels | width, height, ppi; optional bleed |
| Calculations | print-size-calculator | Print size, effective PPI or required pixels | mode and the two known quantities |
| Calculations | aspect-ratio-calculator | Ratio or matching edge | width, height and requested ratio/edge |
| Image inspection | dpi-checker | Read resolution and field sources | file_id |
| Image inspection | metadata-viewer | Inspect metadata | file_id and sensitive-field choices |
| Image transforms | dpi-converter | Write density metadata | file_id, target DPI |
| Image transforms | image-converter | Encode JPG, PNG or WebP | file_id, output format, quality |
| Image transforms | image-resizer | Resize, crop or pad | file_id, target dimensions and fit |
| Image transforms | metadata-remover | Remove selected metadata | file_id and removal/preservation choices |
| Source and AI analysis | ai-image-detector | Source evidence and selected AI analysis | file_id and explicit analysis scope |
| Source and AI analysis | openai-image-detector | Supported OpenAI provenance signals | file_id |
Upload, process and inspect
Create an API key in your account. Upload an image only when the operation needs one, submit the operation with an idempotency key and inspect the returned job. Short work can complete synchronously; queued work returns a job ID that you can poll.
For example, a print workflow can check density before a metadata-only conversion. A content workflow can inspect a source report before deciding whether to request a model analysis. Keep the reported warnings and status with the result instead of treating every HTTP response as a successful image decision.
Count business results, not polling requests
A successful standard API operation uses one credit. Batch work is accounted for by completed items. Polling and retries using the same idempotent operation do not represent new work. A valid but inconclusive model analysis can still be completed work; an upstream failure cannot be relabeled as an inconclusive finding to hide a technical error.
Frequently asked questions
Are local web tools and the API priced identically?
No. The local web tools are free; hosted API processing uses credits.
Can I send an arbitrary image URL?
No. Upload a supported file and use its private file ID.
Does a model result identify the exact generator?
Only report a provider’s available fields and their meaning. A generator prediction is not a verified origin, and unavailable fields are not fabricated.