The image pipeline is already connected
Uploads, queues, resize jobs, optimized outputs, tiles, metadata, and signed downloads are already wired together.
Hosted image processing API
Image processing that gets out of your way
Upload an image, send the job your app needs, and get back usable artifacts without turning image handling into a side project.
A short first run
Verify the account, create a runtime key, upload a source image, and poll the job until the artifact is ready.
A focused account area
API keys, usage, billing, and settings each have one clear place, so setup stays easy to scan.
First run
From account to artifact without setup sprawl
The first trip is intentionally short: verify, create a runtime key, send a job, and fetch the output.
1. Create and verify the account
After verification, choose Starter or Growth to activate API access.
2. Issue a runtime key
Create an `api_runtime` key from API Keys for uploads, jobs, polling, artifact metadata, and signed downloads.
3. Upload and process
Upload source assets, create async jobs, poll them, then read artifact metadata and signed download URLs from the API host.
Docs
Use the quickstart-first docs path
The docs center starts with the first successful artifact, then branches into the rest of the product model only when you need more detail.
1. Getting Started
Create the account and first key, then send the first request.
2. AuthenticationUse the right credential model for people, sessions, and API clients.
3. Uploads and JobsBuild the async upload and processing path without guessing at payload shape or request flow.
4. Artifacts and DownloadsRead artifact metadata and use signed download URLs the way the service expects.
5. WordPress Grid IntegrationConnect a server-side WordPress grid workflow for hosted rendering and optional CDN tile delivery.
Support path
Choose the right help path
Use docs for API setup, account settings for common help, and contact for product or plan guidance.
Read the docs first
Use the quickstart and API guides when you are setting up the first key, upload, job, and artifact flow.
Use account settings for common questions
Once you have an account, use Settings for documentation, billing, access, and privacy links.
Use contact for product, integration, privacy, or legal questions
Contact ImageGrid when you need help evaluating a fit, clarifying a workflow, or going beyond the quickstart and account UI.
Built for
For teams with image work in the critical path
ImageGrid is intentionally narrower than a full media platform. It focuses on the upload-to-artifact flows most apps need first.
Your marketplace needs dependable variants
Generate thumbnails and optimized formats without making the product team own another image pipeline.
Your viewer needs tiles
Turn large images into tile workflows that fit map, archive, publishing, and inspection interfaces.
Your app needs artifact metadata it can trust
Keep source uploads, derivative metadata, and signed delivery predictable enough for backend integrations and automated tools.
Your grid workflow needs hosted rendering
Move large grid renders off the application server while keeping local fallback behavior and optional signed CDN tile delivery.