Twitter (X) Screenshot Generator

What it returns

59 fields from the published dataset schema. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

• typescreenshot for a captured image, status for a failure/run message, runSummary for end-of-run totals.
• targetUrlThe Twitter/X post or profile URL that was captured
• profileUrlThe profile URL when a profile was captured
• captureModepostCard, thread, profileHeader (header only) or fullProfilePage (loaded preview)
• statusResult status (success or a friendly error description)
• codeTyped failure code: not_found, protected, deleted, login_wall, wrong_author, wrong_target, selector_miss, media_error, browser_crash, network_error, invalid_input or capture_error
• messageHuman-readable failure message
• billableTrue only for captured screenshot rows; status and summary rows are not billable
• accessStatepublic, protected, deleted, not_found or login_wall
• requestedUrlThe input URL as requested, when the canonical URL differs
• canonicalUrlThe canonical X URL X actually served
• effectiveScaleActual image pixels per CSS pixel (image width / clipped CSS width)
• previewLimitedTrue when a profile capture hit the logged-out preview cap
• previewLimitReasonWhy the profile capture is a preview rather than the full timeline
• threadThread capture details: focalIndex, threadAuthor, threadLength, threadParts, gateIndex, threadComplete, truncatedReason (non_author_reply, gate, max_height, dpr_height_limit or no_parts)
• threadIdFocal post id for a thread capture
• capturedPostCountPosts rendered in the profile capture
• profilePostCountPost count shown in the profile header
• requestedTargets requested in the run
• capturedScreenshots captured in the run
• failedTargets that failed with a typed status code
• skippedInputs dropped during validation
• billableScreenshotsNumber of captured, billable screenshots in the run
• failureCodesCount of each typed failure code
• invalidInputsInputs dropped during validation with a reason
• totalBytesCombined size of all captured images
• widthWidth of the captured image in pixels
• heightHeight of the captured image in pixels
• filenameFile name of the screenshot in the key-value store
• downloadUrlPublic signed HTTPS URL to download the screenshot file (omitted for local file:// URLs and when signing fails)

Not in the schema among the core X (Twitter) fields: post_id, text, posted_at, likes, reposts. The field matrix shows which other tools return them.

How it differs from the other X (Twitter) Actors

Among the 12 catalogue Actors for X (Twitter) with a published schema, only this one returns captureMode, billable, effectiveScale, previewLimited, previewLimitReason, thread, threadId, requested.

Pick another Actor if you need

Input

Example input

Built from the input form's published example values and defaults.

{
  "postUrls": [
    "https://x.com/NASA/status/2107095768821576019"
  ],
  "tweetUrls": [],
  "profileUrls": [],
  "captureMode": "postCard",
  "theme": "dark",
  "bothThemes": false,
  "includeEvidence": false,
  "fullPage": false,
  "hideReplies": true,
  "includeMetadata": false,
  "format": "png",
  "quality": 90,
  "deviceScaleFactor": "1x",
  "viewportWidth": 1440,
  "viewportHeight": 900,
  "maxThreadHeight": 8000
}

Run it from code or an AI agent

The same run through the Apify API, with the example input. You need an Apify API token; the run is billed to your account at the Store price.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "postUrls": [
        "https://x.com/NASA/status/2107095768821576019"
    ],
    "tweetUrls": [],
    "profileUrls": [],
    "captureMode": "postCard",
    "theme": "dark",
    "bothThemes": False,
    "includeEvidence": False,
    "fullPage": False,
    "hideReplies": True,
    "includeMetadata": False,
    "format": "png",
    "quality": 90,
    "deviceScaleFactor": "1x",
    "viewportWidth": 1440,
    "viewportHeight": 900,
    "maxThreadHeight": 8000
}

run = client.actor("nimbryxo-studio/twitter-x-screenshot-generator").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "postUrls": [
        "https://x.com/NASA/status/2107095768821576019"
    ],
    "tweetUrls": [],
    "profileUrls": [],
    "captureMode": "postCard",
    "theme": "dark",
    "bothThemes": false,
    "includeEvidence": false,
    "fullPage": false,
    "hideReplies": true,
    "includeMetadata": false,
    "format": "png",
    "quality": 90,
    "deviceScaleFactor": "1x",
    "viewportWidth": 1440,
    "viewportHeight": 900,
    "maxThreadHeight": 8000
};

const run = await client.actor("nimbryxo-studio/twitter-x-screenshot-generator").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/nimbryxo-studio~twitter-x-screenshot-generator/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"postUrls":["https://x.com/NASA/status/2107095768821576019"],"tweetUrls":[],"profileUrls":[],"captureMode":"postCard","theme":"dark","bothThemes":false,"includeEvidence":false,"fullPage":false,"hideReplies":true,"includeMetadata":false,"format":"png","quality":90,"deviceScaleFactor":"1x","viewportWidth":1440,"viewportHeight":900,"maxThreadHeight":8000}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=nimbryxo-studio/twitter-x-screenshot-generator",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

What a run costs

The result rate falls on higher Apify plans. Each figure is the published per-result rate times the number of results.

• Every run also has a start event, charged per GB of memory (minimum one): $0.10 on Free, $0.03 on Business. At its default memory of 4 GB a run starts at $0.40 on Free. Fewer, larger runs keep this small.
• The Free plan includes $5 of monthly usage (Apify pricing, checked 2026-11-11); at the Free rate that covers at most about 5,050 results, less start events and platform usage.
• Worked example: 10,000 results in one run on the Free plan cost $10.30 ($9.90 for results + $0.40 start), plus Apify platform usage (compute), billed separately by Apify.
• Pay per event. Platform usage (compute) is billed by Apify on top of the event prices. Compare other tools in the cost estimator.

Where it fits among X (Twitter) routes

It ranks 10 of 12 catalogue Actors for X (Twitter) on the published formula (fields, price, reliability, freshness). Its line is highlighted on the map.

What people use it for

X screenshot records provide captured post or profile URLs, image filenames, dimensions, capture timestamps and download links when available, alongside status and summary rows. Reports that need a rendered post card, contiguous same-author thread or profile header benefit from these captures, while the catalogue's lookup and media tools return structured post data or source media files.

The published schema requires no input; use postUrls or profileUrls to specify public X posts or profiles to capture.

• Illustrate a report with post captures identified by targetUrl, filename and capturedAt.
• Compare saved profile captures using profileUrl, capturedPostCount and previewLimited.
• Review capture failures by code and accessState, then compare them with captured and failed run totals.
• Capture post screenshots
• Capture profile screenshots
• Preserve public evidence

Tips

• Set captureMode to select a post card, thread, profile header or loaded profile preview.
• Enable bothThemes to capture each target in dark and light, with separate files and screenshot rows for each theme.

Other catalogue Actors for X (Twitter)

Similar Actors

Questions people ask

Sources

• Twitter (X) Screenshot Generator on Apify Store
• Published build with input and output schema (JSON)
• X API v2 documentation