Not finding your answer here? Please email us: email@example.com. We enjoy helping people debug their HTML.
Table of contents
- Is there a rate limit?
- Why is my image twice as large as expected?
- Can you provide an SLA?
- I need to generate a large amount of images one time, which plan should I use?
- Can I use external CSS stylesheets?
- Can I use my own Font Awesome Pro icons?
- How do I render an entire webpage?
- How long will my image URL work?
- Can I load external images?
- How do I upgrade my account?
- Do you support Chinese, Japanese and Korean characters?
- How much bandwidth can I use?
- Can I use the API for a hackathon?
- Can I set my images filename?
- What version of Google Chrome does HCTI use?
- I have other questions, who do I ask?
No rate limits here. You’ll be able to create images up until you reach your account limit.
By default we render images for high resolution screens. This is known as
@2X. This ensures your image looks great on devices like iPhones and high resolution monitors.
You can adjust this back to
@1X by setting
device_scale:1 when creating your image.
Absolutely. All of our enterprise plans include an SLA. Contact us at firstname.lastname@example.org and we can build a custom plan for your specific needs.
If an existing monthly plan does not fit your needs, please email us at: email@example.com with the number of images you need to generate. We can send you a one time invoice and credit your account with the number of images you need to generate.
Yes, embed the
link tag in your HTML and it will be loaded on render. Multiple CSS files are supported. Large files may slow down initial render time. See this CodePen for an example.
link tag in your HTML and it will be loaded on render.
Yes, include the
<link> tag to the Font Awesome CDN in your html. You may need to add
localhost to your hostname whitelist for us render icons using your account.
We recommend passing the
url to your webpage to the API. Learn how to do that here: .
Alternatively, when passing your HTML to the API, include the full HTML markup. Starting and ending with the
<html> tags. The HCTI API will enter full page mode and render the entire page as displayed by Google Chrome.
Forever. As long as your HCTI account is active, we keep a copy of your generated image stored and accessible from your image url.
Yes, be sure to include the full URL to your external image. The API will load it before creating the image.
<img src="https://example.com/yourimage.png" />
You may change your plan anytime by visiting the Dashboard.
Yes. We have Noto CJK installed in our image renderer. If you find any language/character set that does not render correctly, please send us an email and we’ll get it added for you.
All images served by the hcti.io domain are cached by Cloudflare’s global content delivery network. Bandwidth is unlimited and paid for as a part of your subscription.
Definitely. If you’re a student and using the API to build something cool. Email us and we’d be happy to add free images to your account.
The filename for your image is a randomly generated (and unique!) UUID. We currently do not have the option to set the filename.
v1/image namespace is shared by everyone who uses the API. Auto generating the file names makes your content more secure (hard to guess). We also use these long keys as partition keys for our infrastructure. This helps us scale the API for creating millions of images each month.
Using UUID’s helps us keep the service easy to use, fast and secure. Which is important to us.
We regularly keep HCTI up-to-date with the latest version of Chrome. We run a full test suite to ensure images render as expected before upgrading the API.
Email us! firstname.lastname@example.org. We’d love to hear from you. We’re great at debugging rendering issues, send us your toughest problems.