ImageGrid.dev

Hosted image-processing API

Sign in Create account

Documentation

FAQ

Check current scope, support expectations, product limits, and the fastest docs-to-contact path.

Read this page as markdown OpenAPI JSON Open docs search

Last updated: July 17, 2026

ImageGrid is a hosted image-processing API for developers who want a practical upload-to-artifact workflow without building and operating the entire pipeline themselves.

What is ImageGrid?

ImageGrid focuses on source-image uploads, asynchronous jobs, resize and rescale operations, optimization, tile generation, artifact metadata, and signed downloads.

The goal is to give product teams a practical production-ready workflow for image processing, artifact handoff, and large-image jobs without forcing them to build a custom media backend first.

What can I do with it today?

Today you can:

  • create and activate a customer account
  • issue runtime API keys
  • upload source images
  • submit async resize, optimize, tile, grid_render, and tile_patch jobs
  • poll job state and read artifact metadata
  • use signed download URLs for generated outputs
  • connect server-side WordPress grid workflows for hosted rendering and optional signed CDN tile delivery

Start with Getting Started, then move into Uploads and Jobs and Artifacts and Downloads.

What is the current product boundary?

ImageGrid is for uploaded image processing and generated artifacts. It is not trying to be every media product at once.

The current product does not include:

  • AI image generation or AI-assisted editing
  • unrestricted remote URL ingestion
  • a full CDN-backed media hosting product

Is ImageGrid self-serve or sales-led?

The core integration path is self-serve. Create an account, verify the email, activate a plan, issue a runtime key, and start with the quickstart plus API docs.

If you need help choosing a plan, confirming a workflow, or reviewing a larger workload, use the normal support path instead of waiting on a sales handoff.

Does ImageGrid have a free tier?

ImageGrid does not have an ongoing public free tier. Approved alpha testers can receive a dedicated test account with an expiring runtime API key and a selected Starter, Growth, or custom-safe limit preset. Test access expires after 90 days by default.

How does a WordPress integration connect?

Use a server-side WordPress integration that supports the ImageGrid API. Enter https://api.imagegrid.dev and a runtime key in its ImageGrid settings. Keep local rendering as a fallback and use direct signed tiles only when CDN Delivery is active.

Read WordPress Grid Integration for setup, current alpha limits, failure behavior, and a test checklist.

How is CDN Delivery billed?

CDN Delivery costs CA$5/month and includes 100 decimal GB per billing period. Overage is disabled by default. An owner may choose a CA$0–CA$25 whole-dollar monthly cap; usage beyond the included amount costs CA$0.04 per whole GB until delivery reaches the cap and pauses.

Where should API traffic go?

Use the public site for docs and customer access:

  • imagegrid.dev for docs, signup, login, API keys, billing, and settings

Use the API host for integration traffic:

  • api.imagegrid.dev for /v1/* requests, artifact metadata, and signed downloads

The public apex does not serve the customer integration API. Keep documentation and account access on imagegrid.dev, and send integration traffic to api.imagegrid.dev.

What is the support path?

Use the fastest path for the type of help you need:

  1. Read the docs first for setup, auth, upload, job, and artifact questions.
  2. Use the signed-in Settings area for account-specific documentation, billing, access, and privacy links.
  3. Use the public contact page for product, integration, privacy, or legal questions that go beyond the docs and account UI.

If you contact support, include the endpoint, UTC timestamp, X-Request-ID, relevant object ID, workflow, and expected result. Never send an API key or the query string from a signed URL.

What limits should I plan around?

ImageGrid is intentionally focused. That keeps the product clear, keeps pricing understandable, and makes the first integration easier to complete.

The most important limits to plan around are:

  • self-serve plans use processing credits plus hard limits for upload size, output size, generated tiles, retention, and request rates
  • larger grid or tile rebuild workloads may need review before they fit a self-serve plan
  • support is docs-first, with human follow-up through the signed-in product and public contact path