How to Save a Full-Page Website Screenshot to Google Drive with Make

To save a full-page website screenshot to Google Drive with Make, create a scenario that captures the URL with a screenshot provider that supports full-page capture, turns the result into a file if needed, and passes the file name and file data to Google Drive’s Upload a file module. A screenshot URL by itself is not the image file: if your capture service returns a URL, download it in Make before uploading it.

How the workflow fits together

Trigger: run on a schedule, or start when a URL arrives from a form, spreadsheet, or another app.
Capture: send the URL to a screenshot service or API that explicitly supports full-page screenshots.
Prepare a file: map returned binary file data directly, or download the returned image URL with Make’s HTTP module.
Upload: map the filename and file data into Google Drive’s Upload a file module.

Make scenarios connect apps through modules that transfer and transform data. Make’s file guide describes file data as requiring a name and data, and shows downloading a file from a URL before passing it to another module. Make: Working with files.

Choose a screenshot capture method

The capture service determines whether the result includes the whole page. Google Drive’s upload action does not turn a viewport screenshot into a full-page image. Before choosing a provider, verify:

It supports full-page capture, rather than only the visible viewport.
Whether the response contains file data or a URL that Make must download.
How it waits for JavaScript, delayed content, and lazy-loaded images.
Whether it can access pages that require authentication, if your target does.
Supported image formats, output-size limits, pricing, retention, and privacy terms.
How it connects to Make: a maintained native module, an HTTP request, or another supported integration.

Make’s Custom JS integration listing includes a Create Screenshot action described as taking a screenshot of a URL, but the action is marked Deprecated. Check its current availability and choose a maintained capture path. Make: Custom JS and Google Drive integration.

Build the Make scenario

1. Add a trigger and identify the URL

Create a new scenario. Use a schedule for recurring captures, or select a trigger that receives a URL from a form, sheet, or another source. Make sure the URL is available as a mapped value for the capture step. If you want one screenshot per row or submission, arrange the scenario so each incoming URL is processed as its own operation.

2. Add the full-page capture request

Add your chosen provider’s Make module or use an HTTP request module. Configure the target URL and the provider’s documented full-page option. Parameter names and response formats vary by provider; do not assume an option name or that the response is an image file. Check the provider’s current documentation for its endpoint, authentication method, full-page parameter, image format, and wait controls.

For pages that render content after the initial load, use the provider’s documented wait options where available. A fixed delay, a selector wait, or network-idle wait may be offered, but availability and exact behavior depend on the provider. Test pages with content below the fold: some sites load images only as the page is scrolled.

3. Make the result a file

Inspect the capture module’s output. If it returns the image data as a file, use that file object in the next step. If it returns only an image URL, add HTTP > Download a file, map the image URL into its URL field, and use the downloaded file output. Make’s file guide documents this download-then-pass pattern. Make: Working with files.

Choose a filename with the correct extension, such as homepage-2026-10-04.png or homepage-2026-10-04.jpg. Match the extension to the actual response format; changing the filename extension does not convert the image.

4. Upload the file to Google Drive

Add Google Drive > Upload a file.
Create or select the Google account connection when prompted.
Choose the destination location, such as My Drive or Shared With Me, then select the target folder.
Map the filename and file data from the capture module or HTTP download step.
Save the module, run a representative operation, and confirm the image appears in the intended folder.

Make’s Google Drive module documentation covers the available file and folder operations. Its documented modules allow My Drive and Shared With Me; Google Shared Drive selection is available to Google Workspace users. Make: Google Drive modules and Make: Google Drive app.

ScreenshotNeo: capture with one API call

If you want to avoid setting up browser automation, use ScreenshotNeo, a website screenshot API and MCP server. Its API can return a screenshot or PDF, and full-page capture supports lazy images. In Make, add an HTTP request to the API, map the response file into Google Drive’s upload module, and use the API documentation to configure the request: ScreenshotNeo API docs.

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}`);

In a Make scenario, configure the HTTP module using ScreenshotNeo’s documented request parameters and map the returned image file data and a filename such as stripe.webp into Google Drive’s Upload a file module. Store the API key as a connection credential or other protected configuration supported by your Make setup; do not place a live key in a publicly shared scenario description.

ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server gives AI agents tools for screenshots, page information, and PDF capture. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, no card required.

Verify the scenario before scheduling it

Confirm the image shows the whole page, including content below the fold.
Check that below-the-fold images and other delayed content have loaded.
Open the file and verify that its actual format matches its extension.
Confirm the filename is unique enough for repeated runs, or decide whether Drive should replace or keep prior captures.
Verify that the file appears in the selected folder and can be opened.
Check that the captured page is appropriate for the account and access context used by the provider.

Options and edge cases to plan for

Full page versus viewport

Use the provider’s full-page setting for a tall capture. A regular screenshot may only include the visible browser viewport. If the final image is unexpectedly short, confirm the capture parameter and provider support before changing the Drive module.

Lazy-loaded and dynamic content

Pages may fetch images or sections only after scrolling, waiting, or running client-side code. Use documented provider controls for waiting or scrolling, if available, and inspect a representative output. A full-page image can still omit content that the page never loaded.

Authenticated pages

For pages behind a login, confirm that the capture provider supports the required authentication method and that the account is authorized to access the page. Do not assume that the Google Drive connection authenticates the screenshot service to the target website; these are separate connections.

Large files and format

Tall pages can produce large images. Make’s file guide lists maximum file sizes by plan: Free 5 MB, Core 100 MB, Pro 250 MB, Teams 500 MB, and Enterprise 1,000 MB. These operational limits can change, so check Make’s current file documentation before relying on a specific limit. The guide also says that when a limit is exceeded, Make proceeds according to the Enable data loss setting. Choose the file format and any resizing or segmentation options based on the screenshot provider’s documented capabilities and your downstream needs.

Repeated captures and filenames

If a scenario runs repeatedly, a fixed filename may create confusing duplicates or replace an earlier file, depending on the module’s behavior and configuration. Include a date, time, record ID, or other stable identifier in the filename and verify the resulting Drive behavior with a sample run.

Performance, reliability, and cost

Each run may involve a capture request, an optional file download, and a Drive upload. Large full-page images take longer to transfer and can encounter file-size limits. Avoid adding arbitrary long waits unless the capture provider requires them; use the provider’s documented wait mechanism when it fits the page. For scheduled workflows, inspect Make’s run history and the capture response so failures at capture, download, and upload can be distinguished.

Make and Google Drive account requirements, provider pricing, capture limits, file retention, and privacy terms depend on the services and plans you choose. Review the current plan details for each service, especially if the scenario captures many pages or stores sensitive content. The research sources do not establish pricing or behavior for a specific third-party capture provider.

Troubleshooting

Symptom	Likely cause	What to check
The screenshot shows only the top of the page	The provider captured the viewport, or full-page capture was not enabled.	Check the provider’s full-page setting and confirm it supports full-page output.
The image is missing below-the-fold content	The page uses lazy loading or delayed JavaScript content.	Use the provider’s documented wait or lazy-load handling options and inspect a fresh capture.
Drive says required file information is missing	The upload module did not receive both file name and file data.	Map both fields. If the capture step returned a URL, add HTTP > Download a file and pass its file output.
The uploaded file cannot be opened	The filename extension does not match the response format, or the response was not image data.	Inspect the capture response and use the correct file format and extension. Do not treat an error response body as an image.
The scenario cannot access the destination folder	The Google account connection lacks access, or the folder location is not available in that account context.	Reconnect or authorize the intended Google account and select an accessible folder. Shared Drive availability in Make’s documented modules requires Google Workspace.
A large capture fails during transfer	The file may exceed the applicable Make plan limit.	Check the current file-size limit, the actual image size, and the scenario’s Enable data loss setting. Consider provider-supported resizing if suitable.
The deprecated screenshot action is unavailable	Make marks Custom JS Create Screenshot as deprecated.	Use a maintained capture provider or a documented HTTP integration instead.
The file appears in the wrong place or has an unexpected name	The folder or filename mapping points to a different value than intended.	Inspect the mapped fields and run one operation with a recognizable test filename.

FAQ

Can Make itself turn a screenshot URL into a full-page capture?

The Drive upload step stores a file; full-page capture is a capability of the selected screenshot provider. The Make Custom JS Create Screenshot action is listed as deprecated, so verify the current integration before depending on it.

Can I upload a screenshot when my capture service returns a URL?

Yes. Download the URL as a file with Make’s HTTP Download a file module, then map the downloaded filename and data into Google Drive.

Can I save captures in a Google Shared Drive?

Make’s documented Google Drive modules provide Google Shared Drive selection for Google Workspace users. Check the connected account and current module options.

Does changing a file’s extension convert it to PNG or JPEG?

No. The extension should describe the format returned by the capture service. Use a documented conversion step if you need a different format.