How to Automate Website Screenshots with Make Without a Paid Plan

Yes. You can schedule website screenshots with Make’s Free plan by connecting a screenshot service such as HTML/CSS to Image API (HCTI), mapping a page URL into its screenshot action, and sending the generated image to a storage or messaging module. The free setup has two separate limits: Make lists up to 1,000 credits per month and a 15-minute minimum interval between runs; HCTI lists 50 images per month on its Free plan. Neither allowance makes captures unlimited.

This guide walks through a no-code Make scenario, explains how to estimate both quotas, and covers scheduling, delivery, configuration, common problems, and an alternative screenshot API.

1. What the free setup includes

A Make scenario connects a trigger, a screenshot action, and a destination. Make’s integration listings include website screenshot actions, and HCTI documents a Make action named “Create a Screenshot of a URL.” Make describes scheduled screenshot scenarios that send or save the resulting image.

Part	Free allowance or requirement	What to plan for
Make	Up to 1,000 credits per month; 15-minute minimum interval between runs	Scenario runs and all module operations consume credits. Inspect module usage and each run’s details.
HCTI	50 images per month; URL screenshots included; no card required	Each successful image generation uses the screenshot service’s allowance.
Connection	HCTI User ID and API Key	Keep credentials private and store them in the Make connection rather than public exports or screenshots.

Make says its Free plan has no time limit. That means the plan does not expire after a trial period; it does not mean unlimited operations, unlimited captures, or schedules faster than its listed minimum interval. The current figures are from the providers’ official pages checked on 2026-10-03 and can change. See Make pricing, Make integrations, and HCTI pricing.

2. Estimate whether your workflow fits the free limits

Calculate the expected monthly captures first, then separately estimate Make credits. A capture every 15 minutes for a 30-day month would request up to 2,880 captures, far above HCTI’s listed 50 free images. Even one daily capture is about 30 images a month, before retries or additional URLs.

Estimate image volume: captures per day × active days, multiplied by the number of URLs per run. Compare that with HCTI’s 50-image allowance.
Estimate Make usage: count the trigger and each module operation across all scheduled runs. Make’s credit guide says non-AI apps generally use one credit per operation; check the current module’s usage and the run details rather than assuming every screenshot action has the same cost.
Include delivery work: saving a file or sending a message adds scenario operations. More steps and multiple destinations can use credits faster.
Set a cadence: recurring schedules on the Free plan cannot run more frequently than every 15 minutes. A slower schedule can keep image volume within a small allowance.

If either quota is exceeded, the workflow may stop or be limited. A paid allowance or a different service may be needed, but decide only after estimating your actual capture frequency and operations.

3. Build a Make scenario with a URL screenshot action

Step 1: Create a scenario

Create a Make account and start a new scenario. Make says new users are assigned a free account. A scenario is the workflow that runs a trigger, performs the capture, and routes the result.

Step 2: Add the screenshot app and connect it

Add the HTML/CSS to Image app (HCTI) to the scenario and create a connection. HCTI’s Make integration uses the User ID and API Key shown in its vendor dashboard. Treat these as secrets: do not place them in public scenario exports, shared screenshots, or source code.

Step 3: Configure the URL capture

Select Create a Screenshot of a URL and map the target page URL into its URL field. HCTI documents viewport width and height and a delay before rendering as configuration options. Set the viewport to match the output you need; use a render delay only when the page needs extra time to display content. These settings cannot guarantee that every site will render as expected.

For a useful first capture, choose a page that is publicly reachable, specify a complete URL including https://, and start with a conventional desktop viewport. If the page relies on content loaded after navigation, try an appropriate delay. Do not send private pages or credentials unless your workflow is designed to handle them securely.

Step 4: Choose a trigger and schedule

For recurring captures, set a Make schedule at or above the Free plan’s 15-minute minimum interval. For event-led captures, use a webhook or another trigger available to your account and scenario. A webhook is useful when an external event should start a capture; it does not bypass the separate Make credit or HCTI image limits.

Step 5: Route the resulting image

Add a destination module for the service you actually want to use, such as a cloud-drive or messaging app available in Make. Map the generated image output from the screenshot module to the destination’s file or attachment input. Confirm that the destination accepts the output type and file representation provided by the module.

Step 6: Run one scenario execution and inspect it

Run a single scenario execution before enabling a recurring schedule. Inspect each module’s input and output: confirm the URL passed to the screenshot action, that an image was returned, and that the destination received it. Then check Make credit usage and HCTI image usage. Provider documentation describes this workflow; no hands-on account test is represented here.

4. Schedule and delivery patterns

Pattern	How it works	Watch for
Periodic monitoring	Run the scenario on a recurring schedule and capture one or more URLs.	Keep the interval at least 15 minutes on Make Free and multiply the cadence by URLs per run.
Event triggered	Start from a webhook or another available event trigger, then capture the URL.	Bursts of events can consume both Make credits and screenshot images quickly.
Capture and notify	Pass the image output to a messaging destination module.	Check attachment support and whether the destination expects a file, URL, or binary data.
Capture and archive	Pass the output to a cloud storage module.	Choose a predictable folder and filename scheme in the destination, if supported.

Make integration pages describe sending or saving captures, but the exact modules and output mapping depend on the apps available in your account. Confirm the current module fields in Make before building a larger workflow.

5. Configuration choices and edge cases

Viewport and rendering delay

Viewport width and height affect what fits in the captured page and may change responsive layouts. A delay can help when content appears after the initial page load, but waiting longer increases run time and does not fix content that requires interaction, authentication, or a blocked browser. Begin with the smallest useful delay and adjust based on the returned image.

Dynamic, private, and restricted pages

Dynamic content: rotating banners, feeds, and personalized sections can vary between runs. A scheduled screenshot is a point-in-time capture, not a guarantee of identical pixels.
Login-required pages: a plain URL capture may not have the session or access needed to see private content. Do not assume a public URL action can authenticate to an account.
Bot protections: a site may challenge or block automated requests. A longer delay does not necessarily resolve a bot check.
Large pages: long or image-heavy pages may take longer to render and can create larger outputs that are slower to transfer or store.
Multiple URLs: each requested image adds to screenshot usage, while each module operation contributes to Make usage according to its current credit rules.

6. Common errors and fixes

Symptom	Likely cause	What to do
Connection fails	Incorrect HCTI User ID or API Key, or a stale credential.	Copy the current credentials from the HCTI dashboard into the Make connection and reconnect. Keep them private.
Capture action rejects the URL	URL is incomplete or malformed.	Use a fully qualified URL such as `https://example.com/` and check for accidental spaces.
Image is blank or incomplete	Page content loads after the capture, is blocked, or depends on a session.	Check the URL in a normal browser, try a modest render delay, and verify whether the content is publicly accessible.
Scenario succeeds but nothing is delivered	The destination is mapped to the wrong screenshot output field or expects a different file format.	Inspect the screenshot module output and map the image/file field the destination expects.
Scenario stops after working previously	Make credits or HCTI image allowance may have been reached, or the scenario has an execution error.	Review Make usage and run details, then check HCTI usage and plan-credit responses. Reduce frequency or URL count if needed.
Scheduled run cannot use a shorter interval	Make Free plan’s listed minimum interval is 15 minutes.	Use a 15-minute-or-longer schedule or estimate whether another allowance is needed.
Results vary from run to run	The site content or responsive layout changes over time or by viewport.	Use a consistent URL, viewport, and timing, and account for genuinely dynamic page content.

7. Performance, reliability, and cost

Faster schedules increase both the number of images and the number of scenario operations. A 15-minute schedule is the shortest interval listed for Make Free, but that does not make it economical under HCTI’s 50-image free allowance: at that cadence, one URL would consume the monthly image allowance in less than a day. Lower-frequency checks are a better fit for a small free quota.

Rendering delay can improve the chance that late-loading content appears, but it adds time and cannot guarantee success. Make and the screenshot provider are separate services with separate quotas and possible failure points. Check execution history and both usage meters routinely; for important monitoring, decide how to handle missed runs, duplicate notifications, and outages in the destination workflow.

For current Make credit rules, consult the Make credits guide. HCTI documents API usage and plan limits in its API documentation. Recheck both providers’ current pricing and module availability before relying on a particular allowance.

8. Or skip the browser setup

If you need an API call instead of wiring a Make scenario, ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns an image or PDF. The examples below use the documented endpoint and save the response as a WebP file; see the ScreenshotNeo API documentation for options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
Bot checks, blank pages, and failed loads are never billed; response headers say the page verdict and whether it was billed.
An MCP server lets AI agents use screenshot and page information tools.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000 screenshots.

9. Frequently asked questions

Can Make run a screenshot scenario for free indefinitely?

Make says its Free plan has no time limit, but it has monthly credits and a 15-minute minimum run interval. Connected services have their own limits as well.

Does Make provide the screenshot allowance?

Make provides the automation platform and its credit allowance. In this example, HCTI provides screenshot generation and lists 50 free images per month.

Can I take a screenshot every minute on Make Free?

No. Make lists a 15-minute minimum interval between runs on the Free plan.

Will a render delay make every website capture correctly?

No. It is a configuration option for timing; pages may still require access, interaction, or resources the capture cannot reach.

Do I need a paid plan?

Not necessarily. Estimate the monthly captures, Make operations, and needed schedule first. If those exceed either free allowance, then compare a paid allowance or another service against the workflow you need.