Yes. You can schedule website screenshots in a Make scenario without paying Make, using a screenshot service such as HTML/CSS to Image API (HCTI) and a destination module to save or send the resulting image. The free setup has two separate limits: Make’s Free plan allows up to 1,000 credits per month and a 15-minute minimum interval between runs; HCTI’s Free plan lists 50 images per month. Neither allowance makes the workflow unlimited.
What you need—and what “free” covers
The no-code workflow is a Make scenario with three parts: a trigger or schedule, a screenshot action that captures a URL, and an output module that stores or sends the image. Make lists URL screenshot actions in its HTML to Image and HTML/CSS to Image app listings. HCTI documents a Make action called “Create a Screenshot of a URL.” Make’s HTML to Image integration listing and HTML/CSS to Image integration listing describe these integrations.
As an Amazon Associate I earn from qualifying purchases.
There are two independent free allowances to monitor:
Recommended Free Tools
| Service | Free allowance relevant to this workflow | What it limits |
|---|---|---|
| Make | Up to 1,000 credits per month; 15-minute minimum interval between runs. Make’s pricing page, checked in 2026. | Scenario activity. Make says the Free plan has no time limit. |
| HCTI | 50 images per month; URL screenshots are included, and no card is required. HCTI’s pricing page, checked in 2026. | Screenshot generation, separately from Make credits. |
Make’s credit guide says non-AI apps generally use one credit per operation, but do not assume every screenshot action always has the same cost. Check the module’s current usage and the run details. See Make pricing, HCTI pricing and Make’s credit documentation.
#1 Best Overall
Set up a recurring screenshot scenario
- Create a Make account and scenario. Make says new users are assigned a free account. Start a new scenario in Make and add a module to it. The Free plan has a 15-minute minimum interval between scheduled runs; it does not support a shorter recurring schedule. See Make pricing and the Make integration listing.
- Add the HCTI screenshot action and connect your account. Search Make’s app catalog for HTML/CSS to Image, then select “Create a Screenshot of a URL.” When prompted to create a connection, enter the HCTI User ID and API Key available in your HCTI dashboard. Treat both as credentials: do not expose them in a public scenario export or screenshot. HCTI’s Make integration guide documents the connection.
- Map the page URL. Enter a fixed URL or map one supplied by an earlier module. HCTI accepts a URL for capture. Its API documentation also describes viewport width and height and a delay before rendering; these options can help match a desired layout or allow a page extra time to render, but they do not guarantee that every site will render correctly. See HCTI API documentation.
- Choose a schedule or event trigger. For routine monitoring, set the scenario schedule to an interval Make allows on its Free plan—no more often than every 15 minutes. For event-driven captures, use a webhook or another available trigger rather than polling on a schedule. Trigger availability depends on the modules and workflow you choose; Make’s integration pages show scheduled screenshot workflows and delivery examples.
- Add a destination module. Add the cloud-drive or messaging app you actually use, then map the generated image output from the screenshot module into its file or message field. Make’s integration pages describe saving or sending captures; the exact fields depend on the destination module you select.
- Test once and inspect the run. Run the scenario with a page you can access and check that the screenshot module returns an image and the destination receives it. Confirm the output format and any destination-specific file requirements in your selected modules before relying on a recurring run.
- Track both allowances. Monitor Make credits and HCTI image usage separately. HCTI’s API documentation describes plan-credit limits and usage responses; a limit reached at either service can stop or constrain the workflow. See HCTI API documentation and Make’s credit guide.
Estimate whether the free limits fit
Estimate the captures first, then account for the rest of the scenario:
- HCTI image allowance: compare planned captures per month with its listed 50 images per month. If a scenario captures multiple URLs in one run, count the images generated, not only the scenario runs.
- Make credit allowance: include the screenshot action and every other module operation that runs. Make’s general guide says non-AI apps generally use one credit per operation, but check the actual module’s current credit use and each run’s details rather than treating that as a guaranteed per-screenshot price.
- Schedule: Make’s Free plan’s 15-minute minimum interval is the shortest recurring schedule stated on its pricing page. A schedule at that minimum would run up to 96 times in a 24-hour day if left enabled continuously, before considering other workflow operations; that frequency would exceed HCTI’s 50-image monthly allowance if each run produced one image.
A low-volume workflow may fit both allowances; exceeding one does not automatically mean the other is exceeded. If the expected image count is above 50, the desired recurring interval is shorter than 15 minutes, or the full scenario would exceed Make’s credits, compare the applicable service allowances and paid options against your actual workload before changing plans. Make says the Free plan has no time limit, but that does not remove its usage limits. See Make pricing and HCTI pricing.
Common problems and fixes
- The screenshot module cannot connect: verify that the HCTI User ID and API Key are copied from the vendor dashboard and that the connection was saved. Do not share those credentials in exported scenarios or public screenshots. HCTI lists these credentials for its Make integration in its integration guide.
- The output is blank or missing page content: check that the URL is correct and accessible to the screenshot service. If the page needs more time to render, try the documented delay option; adjust viewport width and height if the layout is not what you expect. These settings can help with rendering but cannot guarantee success on every site. See HCTI API documentation.
- The destination receives no usable image: inspect the scenario run to confirm the screenshot action produced an image, then check that you mapped that output to the destination module’s expected file or message field. Field names and requirements vary by destination.
- Runs stop or usage is constrained: check Make’s credit usage and HCTI image usage independently. Compare Make’s run details with its credit guide and consult HCTI’s API documentation for plan-credit and usage responses. A remaining allowance at one provider does not imply a remaining allowance at the other.
- You need a faster recurring schedule: the Make Free plan’s stated minimum interval is 15 minutes. Choose an event trigger if the workflow is naturally event-led, or assess whether another applicable allowance or service meets the required cadence.
Or skip the browser setup
If you would rather call a screenshot API directly than connect Make modules, ScreenshotNeo takes a URL in one GET request and returns a screenshot or PDF. For a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo API documentation for the request options. ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; these steps can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides screenshot tools for Claude, Cursor and other MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots per month, no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Can a Make Free scenario run more often than every 15 minutes?
No. Make lists a 15-minute minimum interval between runs for the Free plan. An event trigger is a different workflow pattern, not a faster recurring schedule.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDoes the HCTI free allowance reset independently of Make credits?
Yes. HCTI’s image allowance and Make’s scenario credits are separate service limits, so monitor each account’s usage.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
