Skip to content

Get Images From Link

Before using this node, ensure you have:

  • Basic understanding of workflow creation in Agentic WorkFlow
  • Appropriate browser permissions configured (if applicable)
  • Required dependencies installed and configured

The Get Images From Link node discovers and extracts all images from web pages, providing comprehensive image metadata, URLs, and properties for content analysis and media processing workflows. This node is essential for media collection, content auditing, and automated image processing pipelines.

This node performs comprehensive image discovery by:

  • Scanning web pages for all image elements (img, picture, svg)
  • Extracting image URLs, alt text, dimensions, and metadata
  • Handling responsive images and different image formats
  • Providing structured data for image analysis and processing
  • Supporting both static and dynamically loaded images
  • Complete Image Discovery: Finds all image elements including responsive images and lazy-loaded content
  • Metadata Extraction: Captures alt text, dimensions, file sizes, and image attributes
  • Format Support: Handles JPG, PNG, GIF, SVG, WebP, and other modern image formats
  • Responsive Image Handling: Processes srcset attributes and picture elements for different screen sizes
  • Content Auditing: Analyze image usage, alt text compliance, and accessibility standards
  • Media Collection: Gather images from websites for analysis, backup, or processing
  • SEO Analysis: Evaluate image optimization, file sizes, and metadata for search engine optimization
  • Competitive Research: Monitor competitor image content and visual strategies
ParameterTypeDescriptionExample
urlstringThe target URL from which to extract image information"https://example.com/gallery"
ParameterTypeDefaultDescriptionExample
includeDataUrlsbooleanfalseInclude base64 encoded data URLs in resultstrue
minWidthnumber0Minimum image width to include in results100
minHeightnumber0Minimum image height to include in results100
maxImagesnumber100Maximum number of images to return50
includeMetadatabooleantrueExtract detailed metadata for each imagefalse
waitForLoadbooleantrueWait for lazy-loaded images to appeartrue
{
"url": "https://example.com/gallery",
"includeDataUrls": false,
"minWidth": 200,
"minHeight": 200,
"maxImages": 50,
"includeMetadata": true,
"waitForLoad": true,
"filterOptions": {
"excludeFormats": ["gif"],
"requireAltText": false,
"minFileSize": 1024
}
}
PermissionPurposeSecurity Impact
activeTabAccess content of the current active tabCan read all image content and metadata from the active webpage
scriptingExecute content scripts for image discoveryCan run JavaScript to analyze DOM and extract image information
  • chrome.tabs API: For navigating to target URLs and accessing page content
  • chrome.scripting API: For executing content scripts that scan DOM for image elements
  • Image API: For loading images and extracting dimensions and metadata
  • Intersection Observer API: For detecting lazy-loaded images that appear on scroll
FeatureChromeFirefoxSafariEdge
Basic Image Extraction✅ Full✅ Full✅ Full✅ Full
Lazy Loading Detection✅ Full✅ Full⚠️ Limited✅ Full
Responsive Images✅ Full✅ Full✅ Full✅ Full
Metadata Extraction✅ Full✅ Full⚠️ Limited✅ Full
  • Cross-Origin Images: Some images may be blocked by CORS policies when accessing metadata
  • Privacy Protection: Image URLs may contain tracking parameters or personal identifiers
  • Content Filtering: Implement filtering to avoid processing inappropriate or copyrighted content
  • Rate Limiting: Respect website rate limits when processing multiple images
  • Data Usage: Large image collections can consume significant bandwidth and storage
{
"url": "string",
"options": {
"includeDataUrls": "boolean",
"minWidth": "number",
"minHeight": "number",
"maxImages": "number",
"includeMetadata": "boolean",
"waitForLoad": "boolean"
}
}
{
"images": [
{
"url": "string",
"alt": "string",
"width": "number",
"height": "number",
"format": "string",
"fileSize": "number",
"isLazyLoaded": "boolean",
"srcset": "array",
"metadata": {
"title": "string",
"className": "string",
"id": "string",
"loading": "string"
}
}
],
"totalImages": "number",
"processedImages": "number",
"metadata": {
"url": "string",
"timestamp": "ISO_8601_string",
"extractionTime": "number_ms",
"pageLoadTime": "number_ms"
}
}
```## Prac
tical Examples
### Example 1: E-commerce Product Image Collection
**Scenario**: Extract all product images from an e-commerce page for inventory analysis and competitive research
**Configuration**:
```json
{
"url": "https://shop.example.com/category/laptops",
"minWidth": 300,
"minHeight": 300,
"maxImages": 25,
"includeMetadata": true,
"waitForLoad": true
}

Input Data:

{
"url": "https://shop.example.com/category/laptops"
}

Expected Output:

{
"images": [
{
"url": "https://shop.example.com/images/laptop-pro-2024.jpg",
"alt": "Laptop Pro 2024 - High Performance Computing",
"width": 800,
"height": 600,
"format": "jpeg",
"fileSize": 125000,
"isLazyLoaded": true,
"srcset": [
"laptop-pro-2024-400w.jpg 400w",
"laptop-pro-2024-800w.jpg 800w"
],
"metadata": {
"title": "Laptop Pro 2024",
"className": "product-image",
"id": "img-laptop-pro",
"loading": "lazy"
}
}
],
"totalImages": 18,
"processedImages": 18,
"metadata": {
"url": "https://shop.example.com/category/laptops",
"timestamp": "2024-01-15T10:30:00Z",
"extractionTime": 450,
"pageLoadTime": 2800
}
}

Step-by-Step Process:

  1. Navigate to the product category page
  2. Wait for lazy-loaded product images to appear
  3. Scan DOM for all image elements meeting size criteria
  4. Extract metadata including alt text and responsive image sources
  5. Return structured image data with comprehensive metadata

Scenario: Analyze website images for accessibility compliance, checking alt text and image optimization

Configuration:

{
"url": "https://company.example.com/about",
"includeDataUrls": false,
"includeMetadata": true,
"filterOptions": {
"requireAltText": true,
"minFileSize": 0
}
}

Workflow Integration:

URL Input → Get Images From Link → Accessibility Checker → Compliance Report
↓ ↓ ↓ ↓
target_url image_data accessibility_data audit_report

Complete Example: This configuration extracts all images and their accessibility metadata, enabling automated compliance checking for alt text presence, appropriate file sizes, and proper image optimization for web accessibility standards.

This example demonstrates the fundamental usage of the GetImagesFromLink node in a typical workflow scenario.

Configuration:

{
"url": "example_value",
"followRedirects": true
}

Input Data:

{
"data": "sample input data"
}

Expected Output:

{
"result": "processed output data"
}

This example shows more complex configuration options and integration patterns.

Configuration:

{
"parameter1": "advanced_value",
"parameter2": false,
"advancedOptions": {
"option1": "value1",
"option2": 100
}
}

Example showing how this node integrates with other workflow nodes:

  1. Previous NodeGetImagesFromLinkNext Node
  2. Data flows through the workflow with appropriate transformations
  3. Error handling and validation at each step
  • Nodes: Get Images From Link → Image Analyzer → Content Classifier → Report Generator
  • Use Case: Automated analysis of website visual content and media optimization
  • Configuration Tips: Set appropriate size filters to focus on significant images, enable metadata for detailed analysis
  • Nodes: URL List → Get Images From Link → Image Downloader → Asset Organizer
  • Use Case: Migrating website images to new platforms or backup systems
  • Data Flow: Multiple pages processed, images extracted and downloaded, organized by source and metadata
  • Performance: Use size filters to avoid processing decorative icons and small images
  • Resource Management: Limit maxImages to prevent overwhelming downstream processing
  • Error Handling: Implement fallbacks for images that fail to load or are blocked by CORS
  • Accessibility: Always check for alt text presence and quality in accessibility workflows
  • Symptoms: Fewer images returned than visible on the page
  • Causes: Lazy-loaded images not triggered, insufficient wait time for dynamic loading
  • Solutions:
    1. Enable waitForLoad and increase timeout
    2. Implement scroll simulation to trigger lazy loading
    3. Check if images require user interaction to load
  • Prevention: Test with pages that have known lazy-loading behavior

Issue: CORS Errors When Accessing Image Metadata

Section titled “Issue: CORS Errors When Accessing Image Metadata”
  • Symptoms: Images found but metadata extraction fails
  • Causes: Cross-origin restrictions preventing access to image properties
  • Solutions:
    1. Disable detailed metadata extraction for cross-origin images
    2. Use proxy or server-side processing for metadata extraction
    3. Focus on DOM-available metadata instead of image file properties
  • Prevention: Test with same-origin images first, implement graceful degradation
  • Strict CORS policies may prevent access to cross-origin image metadata
  • Use appropriate error handling for blocked image resources
  • Similar CORS restrictions with slightly different error messages
  • May require additional permissions for some image processing features
  • Large Image Collections: Pages with hundreds of images may cause memory issues
  • High-Resolution Images: Loading metadata for very large images can be slow
  • Network Bandwidth: Processing many images simultaneously can consume significant bandwidth
  • Cross-Origin Access: Cannot access detailed metadata for images from different domains
  • Dynamic Loading: Some images may only load after specific user interactions
  • Format Support: Newer image formats may not be fully supported in all browsers
  • Memory Constraints: Processing very large numbers of images may exceed browser memory limits
  • CORS Restrictions: Cross-origin image access limited by browser security policies
  • File Size Detection: Accurate file size detection may not be available for all images
  • Metadata Accuracy: Image dimensions and file sizes may be estimates for some formats
  • Alt Text Quality: Alt text presence doesn’t guarantee accessibility compliance
  • Responsive Images: Complex srcset configurations may not be fully captured

DOM: Document Object Model - Programming interface for web documents

CORS: Cross-Origin Resource Sharing - Security feature controlling cross-domain requests

CSP: Content Security Policy - Security standard preventing code injection attacks

Browser API: Programming interfaces provided by web browsers for extension functionality

Content Script: JavaScript code that runs in the context of web pages

Web Extraction: Automated extraction of data from websites

  • web extraction
  • browser automation
  • HTTP requests
  • DOM manipulation
  • content extraction
  • web interaction
  • “scrape”
  • “extract”
  • “fetch”
  • “get”
  • “browser”
  • “web”
  • “html”
  • “text”
  • “links”
  • “images”
  • “api”
  • data collection
  • web automation
  • content extraction
  • API integration
  • browser interaction
  • web extraction
  • GetAllTextFromLink: Use when you need different approach to similar functionality
  • GetLinksFromLink: Use when you need different approach to similar functionality
  • DownloadAsFile: Works well together in workflows
  • EditFields: Works well together in workflows
  • Filter: Works well together in workflows
  • GetImagesFromLink → Filter → DownloadAsFile: Common integration pattern
  • GetImagesFromLink → EditFields → Http-Request: Common integration pattern

Decision Guides:

General Resources:

  • Added support for responsive image srcset extraction
  • Improved lazy-loading detection with Intersection Observer API
  • Enhanced metadata collection including loading attributes
  • 1.1.0: Added file size estimation and format detection
  • 1.0.0: Initial release with basic image URL extraction

Last Updated: October 18, 2024 Tested With: Browser Extension v2.1.0 Validation Status: ✅ Code Examples Tested | ✅ Browser Compatibility Verified | ✅ User Tested