Reference

Technical Glossary

Key terms and concepts for screenshot APIs, headless browsers, and web capture technology.

A C D F H J O P R S V W

A

API Key

A unique identifier used to authenticate and authorize access to an API. API keys are typically passed as query parameters or headers with each request, allowing the service to track usage and enforce rate limits.

🔗 In SnapAPI: Every request requires an api_key parameter. Get yours free from the dashboard. Keys are scoped per user and can be rotated anytime.

AVIF

AV1 Image File Format — a modern, royalty-free image format based on the AV1 video codec. AVIF offers 50% better compression than JPEG and 20% better than WebP at similar visual quality, making it ideal for web performance.

🔗 In SnapAPI: Set format=avif to get screenshots in AVIF format. Excellent for bandwidth-constrained applications — our AVIF screenshots are typically 60-70% smaller than PNG.

C

Chromium

The open-source browser engine that powers Google Chrome, Microsoft Edge, Brave, and many other browsers. Chromium provides the rendering engine used by most headless browser tools for accurate web page capture.

🔗 In SnapAPI: We run the latest Chromium builds on our infrastructure so you don't have to manage browser installations, updates, or security patches. Every capture uses a fresh browser context for isolation.

CSS Injection

The ability to inject custom CSS stylesheets into a web page before rendering. This allows hiding elements, changing layouts, adjusting fonts, or modifying any visual aspect of the page without modifying the source.

🔗 In SnapAPI: Pass custom CSS via the css parameter. Commonly used to hide navigation bars, ads, chat widgets, or style the page specifically for screenshots.

D

Device Emulation

Simulating how a website appears on different devices by configuring viewport dimensions, user agent string, device pixel ratio, and touch capabilities. Used to test responsive designs and capture mobile screenshots.

🔗 In SnapAPI: Choose from 26+ device presets (iPhone 15, Pixel 8, iPad Pro, etc.) with the device parameter, or set custom width, height, and device_scale_factor values.

Device Pixel Ratio (DPR)

The ratio between physical display pixels and CSS logical pixels. A DPR of 2 (common on Retina displays) means each CSS pixel is rendered using 2×2 physical pixels, resulting in sharper images at higher file sizes.

🔗 In SnapAPI: Set device_scale_factor=2 for Retina-quality captures. A 1280×800 viewport at DPR 2 produces a 2560×1600 pixel image. Default is 1.

DOM (Document Object Model)

A programming interface that represents an HTML document as a tree of objects. The DOM allows scripts to dynamically read, modify, add, or delete elements and content on a web page. Modern SPAs heavily rely on DOM manipulation.

🔗 In SnapAPI: Our Extract API can target specific DOM elements via CSS selectors. Use wait_until=domcontentloaded or networkidle to control when the DOM is considered ready.

F

Full Page Screenshot

A capture of the entire scrollable content of a web page, from top to bottom, rather than just the visible viewport area. The resulting image can be very tall for content-rich pages with extensive scrolling.

🔗 In SnapAPI: Set full_page=true to capture the complete page. Useful for archiving, documentation, and visual testing. Combine with AVIF format to keep file sizes manageable.

H

Headless Browser

A web browser without a visible user interface, designed to be controlled programmatically. Headless browsers execute JavaScript, render CSS, handle network requests, and produce output identical to a regular browser — but run in the background without displaying anything on screen.

🔗 In SnapAPI: We manage a fleet of headless Chromium instances so you don't have to. No browser installation, no memory management, no zombie process cleanup. Just call our API and get the result.

J

JavaScript Injection

Executing custom JavaScript code on a web page before or after it loads. Used to manipulate page content, trigger interactions, remove elements, or extract data that requires client-side computation.

🔗 In SnapAPI: Use the js parameter to run scripts before capture. Example: scroll to a section, click a button, expand collapsed content, or remove a modal overlay.

O

OG Tags (Open Graph)

Meta tags in a page's <head> that control how URLs appear when shared on social media (Facebook, Twitter, LinkedIn, Slack, etc.). Key tags include og:title, og:description, og:image, and og:url.

🔗 In SnapAPI: The Extract API can pull OG tags from any URL. Use SnapAPI to generate OG images dynamically — capture a styled HTML template as a 1200×630 PNG.

P

PDF Generation

Converting web pages or HTML content into PDF documents. Browser-based PDF generation respects CSS print stylesheets, page breaks, and layout, producing high-fidelity results compared to template-based PDF tools.

🔗 In SnapAPI: Set format=pdf with options for paper size (pdf_format), margins (pdf_margin), and pdf_print_background. Supports A4, Letter, Legal, and custom sizes.

Playwright

A cross-browser automation framework by Microsoft for end-to-end testing and web scraping. Supports Chromium, Firefox, and WebKit with a single API. Known for auto-waiting, reliable selectors, and parallel execution.

🔗 In SnapAPI: Built on Playwright's Chromium integration for maximum reliability. You get Playwright-level rendering quality without managing browser binaries, dependencies, or infrastructure.

Puppeteer

A Node.js library developed by Google's Chrome team that provides a high-level API to control Chrome/Chromium. Widely used for screenshots, PDFs, web scraping, and automated testing. The most popular headless browser library.

🔗 In SnapAPI: SnapAPI replaces the need to self-host Puppeteer. One API call gets you the same result as 20+ lines of Puppeteer code — with cookie blocking, ad blocking, and format conversion built in.

R

Rate Limiting

A technique to control the number of API requests a client can make within a given time window. Prevents abuse, ensures fair usage, and protects server resources. Typically returns HTTP 429 when limits are exceeded.

🔗 In SnapAPI: Rate limits depend on your plan (Free: 5/min, Starter: 30/min, Pro: 100/min, Business: 500/min). Response headers include X-RateLimit-Remaining so you can pace your requests.

S

Screenshot API

A web service that captures visual representations of web pages as images (PNG, JPEG, WebP, AVIF) or PDFs via simple HTTP API calls. Screenshot APIs abstract away the complexity of running headless browsers, handling JavaScript rendering, managing timeouts, and dealing with edge cases like cookie banners and lazy-loaded content.

🔗 In SnapAPI: That's us! SnapAPI captures pixel-perfect screenshots in milliseconds, with built-in ad blocking, cookie banner removal, 26+ device presets, and multiple output formats. Try it free.

SSRF (Server-Side Request Forgery)

A security vulnerability where an attacker tricks a server into making HTTP requests to unintended internal resources (like localhost, internal APIs, or cloud metadata endpoints). Particularly relevant for screenshot APIs that fetch arbitrary URLs.

🔗 In SnapAPI: We block requests to private IP ranges (127.0.0.0/8, 10.0.0.0/8, 169.254.169.254, etc.), cloud metadata endpoints, and internal services. Every URL is validated and resolved before the browser navigates.

V

Viewport

The visible area of a web page within the browser window. The viewport dimensions determine how the page's responsive layout renders — a 375px viewport triggers mobile styles, while 1920px shows the full desktop layout.

🔗 In SnapAPI: Set width and height to define the viewport (default: 1280×800). Combine with device presets for accurate device emulation including user agent and DPR.

W

Wait Until

A parameter that controls when a web page is considered "fully loaded" and ready for capture. Common strategies include waiting for DOM content loaded, all network requests to complete, or a specific element to appear.

🔗 In SnapAPI: Options include load (default), domcontentloaded, networkidle (wait for network to be idle), or selector:.my-element (wait for a specific CSS selector).

Web Scraping

The automated extraction of data from websites using bots, scripts, or APIs. Modern web scraping often requires a headless browser to handle JavaScript-rendered content, SPAs, and dynamically loaded data.

🔗 In SnapAPI: The Extract API extracts structured data (title, description, metadata, text, markdown) from any URL — no parsing HTML yourself. Combine with screenshots for visual + data capture.

Webhook

An HTTP callback — a POST request sent automatically to a specified URL when an event occurs. Webhooks enable real-time notifications without polling, commonly used for async processing results and integration triggers.

🔗 In SnapAPI: Webhooks are coming soon for async captures. Set a callback URL and receive the screenshot result when it's ready — ideal for long-running captures or bulk operations.

WebP

An image format developed by Google that provides both lossy and lossless compression. WebP images are typically 25-34% smaller than JPEG at equivalent visual quality, with broad browser support (95%+ globally).

🔗 In SnapAPI: Set format=webp for a great balance of quality and file size. WebP is our recommended format for most use cases — it's well-supported and significantly smaller than PNG/JPEG.

Still Have Questions?

Check our docs or reach out — we're here to help.

Read the Docs Contact Us