Proxies
Route Chromium traffic through a configured proxy when a page requires authenticated access or a specific source network.
Proxy and storage credentials
Keep credentials out of image requests
Save authenticated proxies and storage destinations at the organization level. HCTI assigns opaque IDs that requests use for proxy routing and image storage without resending the credentials.
- Authenticated proxies
- Opaque configuration IDs
- Destination-level storage control
Organization settings
Proxy and storage credentials are saved once.
Image request
proxy_id + storage_destination_id
HCTI render
Saved IDs are resolved before Chromium loads the page
Image destination
Your optional storage destination
Page access
Route Chromium through a configured proxy, with authentication when required.
Image storage
Turn on Disable HCTI Storage to keep the rendered image only in your destination.
Security at each step
Control page access and image storage separately
Choose a proxy for browser traffic and a storage destination for the rendered image. HCTI saves each configuration at the organization level and assigns an opaque ID for requests to reference.
Saved credentials
Save proxy passwords and storage credentials once. Image requests send the configuration ID instead of the underlying secrets.
Custom storage
Write generated images to a configured Amazon S3, Cloudflare R2, or S3-compatible storage destination.
Disable HCTI Storage
Send the rendered image to your storage destination without HCTI storing or serving it.
Saved configurations
Configure credentials once, then reference an ID
After you save a proxy or storage destination, image requests use its ID. Connection URLs, usernames, passwords, and storage keys stay out of application payloads.
POST /v1/image
{
"url": "https://internal.example",
"proxy_id": "qz8dV7",
"storage_destination_id": "rK4mxP"
}
Example conversation
MCP connected with OAuth
You
HTML/CSS to Image
HTML/CSS to Image
- You: Use the HCTI MCP to capture this page through my saved production proxy and store the image in my R2 destination.
- HTML/CSS to Image: I’ll reference the saved proxy and storage destination IDs. The request does not need the proxy password or storage credentials.
- You: Use my R2 destination that has Disable HCTI Storage enabled for this screenshot.
- HTML/CSS to Image: The rendered image will be written to your R2 destination without retaining a copy in HCTI storage.
- You: Can future requests reuse those settings without sending the credentials again?
- HTML/CSS to Image: Yes. The proxy and storage configuration stay saved at the organization level, and future requests send only their IDs.
MCP integration
Use the HCTI API from your AI tools
Connect an MCP-compatible AI client to HCTI through OAuth.
Generate images and PDFs, capture webpages, and work with templates without putting an API key in the prompt.
Use cases
Proxy routing and image storage controls
Pages behind a proxy
Use an authenticated proxy to capture pages that HCTI cannot reach directly from the public internet.
Known egress path
Route Chromium traffic through a configured proxy when a site requires a specific source network.
Storage in your account
Write images to your storage destination and, when configured on that destination, prevent HCTI from retaining the rendered file.
Centralized configuration
Let authorized organization members manage proxy and storage credentials while applications send only the opaque IDs shown in the dashboard.
Configure proxies and storage
Keep proxy and storage credentials out of image requests
Save each configuration once, then use its opaque ID on the image requests that need it.
Related features
More ways to use HTML/CSS to Image
Learn about related options for image and PDF generation, storage, security, and team access.