Use Twitter (X) Screenshot Generator with Python

Capture clean screenshots of public X posts and profiles without login. Choose post cards, profile headers or full profile pages, dark/light theme, PNG/JPEG/WEBP output, 2x/3x pixel density and optional profile or post details.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "captureMode": "postCard",
  "deviceScaleFactor": "1x",
  "format": "png",
  "fullPage": false,
  "hideReplies": true,
  "includeMetadata": false,
  "postUrls": [
    "https://x.com/NASA/status/2107095768821576019"
  ],
  "quality": 90,
  "theme": "dark"
}

Download input.example.json and save your reviewed copy as input.json.

Field	Type	Required	Description
`postUrls`	array	optional	Posts to capture as clean post cards. Paste x.com or twitter.com links, bare numeric post IDs, profile links or bare usernames. Any input works in every list.
`tweetUrls`	array	optional	Alias of X post links. Accepts tweet links, bare tweet IDs, profile links and bare usernames.
`profileUrls`	array	optional	Optional. Profiles to capture (header and first posts). Paste profile links, bare usernames, post links or post IDs and the actor routes them to the right capture. Use capture mode to choose header-only or the full page.
`captureMode`	string	optional	What to capture. Post links always produce a single post card; this mode applies to profile links.
`theme`	string	optional	Color theme for the screenshot.
`fullPage`	boolean	optional	When on, the whole page is captured instead of just the post card or the visible profile header.
`hideReplies`	boolean	optional	Hide reply posts so screenshots stay focused on original posts.
`includeMetadata`	boolean	optional	Add details to each row: post id, post URL, author handle, text snippet and the author's follower, following and post counts for posts; username, display name, follower, following and post counts for profiles. Counts are only added when X shows them.
`format`	string	optional	File format of the saved screenshot. JPEG and WEBP support the quality setting; PNG is lossless.
`quality`	integer	optional	Quality for JPEG and WEBP output (1-100). Ignored for PNG.
`deviceScaleFactor`	string	optional	Render the page at a higher pixel density for sharper screenshots. 2x doubles and 3x triples the pixel dimensions.
`viewportWidth`	integer	optional	Browser width used for the capture. Higher values fit more of the page.
`viewportHeight`	integer	optional	Browser height used for the capture.
`proxyConfiguration`	object	optional	Optional. Use a proxy if you plan large runs or see frequent rate limits.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/kcIeUfwCB7DUd1c2b/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

Screenshot capture records for public X posts and profiles, with image dimensions, format, and download link, plus the saved image files.

Questions before you run

Which inputs are required?

No top-level fields are marked required in the published schema. Conditional requirements can still apply; check the README.

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Open on Apify Full Actor reference

Generated from source build MyDjoodZqiGQGH2Jm and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.