Free images

The Assets panel stores images and serves them from the Webflow CDN, but it does not source them. Finding licensed stock photography means leaving your site build. You search a marketplace like iStock, download files, then upload them again. That means switching contexts and manually downloading and re-uploading files while tracking licenses outside the site itself.

The iStock by Getty Images app moves that workflow inside Webflow. You search iStock's library, license an image, and place it on the canvas in one session. For bulk or automated work, the Getty Images API and the Webflow Data API connect the two platforms directly, and both companies now run MCP servers so an agent can drive the same calls.

This integration fits freelance designers, agencies, marketers, students, and small and medium businesses building on Webflow. Enterprise teams and agencies with a Getty Images subscription have a separate companion app. Developers who need automated image pipelines can build via the API.

How to integrate Free images with Webflow

What is Free images? Free images is the label on this Webflow integrations listing, and the service behind it is iStock, a royalty-free stock marketplace operated by iStockphoto LP under Getty Images. Its catalogue covers photos, illustrations, vectors, video footage, and music. The content is licensed, not free: you need an iStock subscription or credits before you can use any of it. iStock sorts everything into two collections, a basic tier of everyday visuals and a premium tier it describes as handpicked, both set out on its plans and pricing page. For images that genuinely cost nothing, Webflow lists a separate Unsplash integration.

Teams pair iStock with Webflow when a project needs licensed, subscription-backed imagery rather than free stock. An agency can source and place every hero image for a client campaign page in one build session. A marketer refreshing a blog can license a hero image per post without a download queue.

The iStock-Webflow integration supports four approaches:

• The iStock by Getty Images app handles search, licensing, and image placement inside Webflow without writing code.
• Assets panel and CMS uploads let you license files on iStock, then add them through the Assets panel, CMS image fields, or a CSV import.
• The iStock affiliate JavaScript widget embeds a strip of iStock search results through a Code Embed element.
• The Webflow and Getty Images APIs give you full control over CMS publishing workflows with automated search and licensing, but require server-side development.

You can mix these approaches depending on how much of the workflow you want automated.

Install the iStock by Getty Images app

The iStock by Getty Images app lets you search, license, and place iStock images without leaving Webflow. Getty Images publishes it, and the Marketplace listing is approved and public, so it is available to every Webflow user. You need an active iStock subscription to license and place images. Without one you can still browse the library inside Webflow, then complete a subscription agreement on the iStock website. The Install app button above opens the listing.

To set up the integration:

1. Install the iStock by Getty Images app from its Webflow Marketplace listing.
2. Open the app from the Apps panel inside Webflow.
3. Open the app menu and sign in, which sends you to iStock or Getty Images to authenticate.
4. Browse and license images using your active iStock subscription.
5. Place the licensed image directly into your design.

Once connected, the app gives you:

• Library search: Search iStock photos and videos from inside Webflow instead of switching to a browser tab and back.
• One step licensing: License and place any content your subscription covers without a download and re-upload cycle.
• Access indicators: A lock icon marks every image that sits outside your active subscription agreement.
• Workspace scope: The listing installs at Workspace level, so one authorization covers the sites in that Workspace.

The content available to you depends on your subscription agreement, and licensing compliance for published pages stays your responsibility. For images you already own or source elsewhere, the manual upload path below covers the rest.

Upload licensed images with the Assets panel and CMS fields

Every iStock download carries a royalty-free license, and websites and web applications sit among the example uses iStock's license agreement permits. That same agreement carries restrictions a Webflow build can walk into, including a clause headed No Standalone File Use, so read it against your own project rather than treating this page as clearance. The Assets panel accepts PNG, JPEG, JPG, GIF, SVG, WebP, and AVIF images up to 4 MB.

Add images through the Assets panel

The Assets panel manages static images and serves them from the Webflow CDN with a public URL. Images uploaded here get automatic responsive variants, which CSV and API uploads do not. High-resolution iStock JPEGs often exceed 4 MB, so compress them before uploading. EPS vectors aren't supported, so export them to SVG in vector software first.

To upload an iStock image:

1. License and download the file from iStock with your subscription or credits.
2. Compress the file if it exceeds 4 MB.
3. Open the Assets panel from the left toolbar, or press J.
4. Click the cloud upload icon and choose the files from your computer.

To swap an image site-wide later, hover over the asset, open more options, choose Replace, and select the new file.

Add images to CMS image fields

For blog heroes, team photos, or any collection-driven content, store licensed images in the Webflow CMS. Image fields accept files up to 4 MB and also generate responsive variants on direct upload.

To set this up:

1. Open Collection settings > New Field and choose Image field (or Multi-image Field for galleries).
2. Upload the licensed iStock file into the field on each collection item.
3. Add an Image element inside a Collection list or Collection page, set Get image from, and select the field.

The image now renders dynamically for every item in the collection.

Bulk import with CSV

CSV import fills CMS image fields from direct URLs, which suits large migrations of already-licensed iStock files. Do not point a CSV at an iStock delivery URL: Getty issues those as short-lived, deliberately opaque links, so the import either fails or breaks soon after. Host the files yourself first, on storage you control such as Amazon S3 or Cloudflare R2.

To import:

1. Upload your licensed images to your own hosting and copy the direct file URLs.
2. Build a CSV with those URLs in the image column; separate multi-image URLs with semicolons. The CSV itself maxes out at 4 MB.
3. Open the CMS panel, select the Collection, and click Import.

CSV-imported images do not receive responsive variants, so upload directly when image quality matters. The View lesson button above opens Webflow's CMS import guide.

Embed the iStock affiliate widget with a Code Embed element

Getty's affiliate partner widget displays a strip of iStock search results that link back to iStock with your affiliate information attached, so it earns referral revenue rather than showing images you have licensed. It needs the affiliate ID and API key issued when you join the affiliate program, and both sit as plain attributes on the element in your page source, so treat that key as public. Code Embed elements also require a Core, Growth, Agency, or Freelancer Workspace, or an active Site plan.

To embed it:

1. Get your affiliate ID and API key through iStock's affiliate program.
2. Drag a Code Embed element onto the page from the Add panel.
3. Paste the script tag and the custom element into the embed, then save.

Getty documents the markup like this:

<script src="https://developer.gettyimages.com/libs/affiliate/1.0/istock.js"></script>

<istock-affiliate api-key="API_KEY" affiliate-id="AFFILIATE_ID"
  search-phrase="trees" item-count="6" orientation="horizontal"
  image-style="photography" image-size="medium"></istock-affiliate>

Getty's own example shows the element self-closed. Write the closing tag as above instead, because a custom element defined through customElements.define will not self-close in HTML. All widget logic runs in the visitor's browser, and each Code Embed element holds up to 50,000 characters.

Build with the Webflow and Getty Images APIs

API access to iStock content runs through the Getty Images API v3 at https://api.gettyimages.com/v3/, and the only iStock-specific routes outside it are two affiliate search endpoints. Getty's technical documentation asks you to contact your Getty Images account representative to discuss API access and licensing options, so budget for a conversation rather than a signup form. This path needs server-side development because it has to protect API secrets and OAuth tokens and move files around. It suits teams automating image sourcing at scale, such as programmatic CMS publishing.

Getty also runs a remote MCP server at https://mcp.gettyimages.com/v1. Its MCP documentation lists tools for authentication, search, asset metadata, and downloads, throttles calls at 20 queries per second, and routes credentials through the same account representative. That documentation scopes search to your organization's Getty Images license agreement, so confirm with Getty whether an iStock agreement is in scope before you design around it. On our side, the Webflow MCP data tools cover the matching asset work, including the two-step upload, alt text updates, and image compression to WebP or AVIF.

Getty Images handles image search and licensing, while Webflow handles asset upload, CMS publishing, and publication triggers:

• Search and licensing: The Getty Images API v3 handles search, asset metadata, and download authorization for iStock content.
• Asset storage: Webflow's Data API takes the licensed file and returns a hosted URL served from the Webflow CDN.
• Content publishing: Webflow creates and publishes the CMS collection items that reference each uploaded asset.
• Event triggers: Register Webflow webhooks on events such as collection_item_published to drive downstream jobs like a license audit log.

Nothing gets pushed back to you. Neither Getty's technical documentation nor its published API specification mentions webhooks, and Asset Changes is a loop your client drives: request a batch of new, updated, and deleted assets for a channel, process it, then confirm it before the next batch is released. Your sync pipeline runs on your schedule rather than Getty's.

Search and license an iStock image

Search runs on an API key alone, but download links require an OAuth access token. Third-party web apps must use the Authorization Code grant rather than Client Credentials.

To fetch a licensed file:

1. Direct the user through the authorization request with your registered redirect URI and PKCE code challenge to start the Authorization Code flow. Then exchange the returned authorization code with POST https://authentication.gettyimages.com/oauth2/token and send grant_type=authorization_code, code, redirect_uri, client_id, client_secret where required, and the PKCE code_verifier.
2. Search with GET /v3/search/images/creative?phrase=<term>&fields=largest_downloads and pass the Api-Key header. The fields=largest_downloads parameter requires the access token.
3. Authorize the download with POST /v3/downloads/images/{id}?auto_download=false to get a 200 response carrying the delivery URI in its body, rather than the 303 See Other redirect that auto_download=true returns.

In the Authorization Code flow, the code challenge belongs in the authorization request, while the code verifier belongs in the token exchange. Access tokens are valid for 30 minutes, per the authorization docs, and the refresh token returned alongside them is long lived, so a well built pipeline never re-prompts the user. Getty's API specification states that download URIs are valid for 24 hours, that the URI should be treated as opaque, and that every download call decrements the allowance on that product offering. Extended licenses are a separate call, POST /v3/asset-licensing/{assetId}, which the specification describes as acquiring an extended license for an asset with iStock credits.

Upload the image to Webflow and publish it to the CMS

You upload assets in two stages with the assets:write scope. The same 4 MB image limit applies, and API-uploaded images do not receive responsive variants.

To implement the pipeline:

1. Call POST /v2/sites/{site_id}/assets with a fileName under 100 characters and an MD5 fileHash. The response returns an uploadUrl and uploadDetails, per the Assets API reference.
2. POST the binary file to the returned Amazon S3 uploadUrl with those details.
3. Create a staged item with POST /v2/collections/{collection_id}/items that references the asset URL. Push it live with POST /v2/collections/{collection_id}/items/publish. Bulk creation via POST /v2/collections/{collection_id}/items/bulk accepts up to 100 items per request.

One licensing clause shapes this architecture. iStock's agreement says that unless you buy an extended license "you may not store the content on a server", meaning a server that gives more than one person simultaneous access, and it adds that these seat restrictions refer to the raw file rather than the end project or use. A published Webflow page is an end use. A shared bucket of licensed originals sitting behind your pipeline is less obviously one. We cannot clear your setup for you, so read that clause against your own architecture and ask iStock where it is not plain.

What you can build with the iStock Webflow integration

Integrating iStock with Webflow lets you license and place stock images inside your build without downloading, tracking, and re-uploading files by hand.

• Campaign microsites: Ship a launch microsite whose hero and section images are licensed and placed in one session, with no download queue sitting between the search and the canvas. Product launch pages and homepage refreshes follow the same shape.
• Client site builds: Agencies and freelancers source hero images for a client project inside the build, and the lock icon flags anything outside the active agreement before it ships. Keep licensing on the subscriber's own account, because iStock's agreement says a subscription is for one named person.
• CMS-driven blogs with licensed heroes: Pair the Getty Images API with Webflow's Data API to run an editorial archive where each post's hero image is licensed, hashed, uploaded, and published in one job.
• Homepage rebrands: License replacement images through the app during a visual refresh. Then use the Assets panel's Replace function to swap an old image everywhere it appears at once.

Use the API path when you want direct control over automated licensing and CMS publishing. Start with our Webflow CMS API guide, then connect the Webflow MCP server so an agent can run the asset upload and publish steps for you.