Feedback
Roadmap
Changelog

Your feedback is our #1 priority!

Let us know how we can make it better for you. 🚀

Seriously, we read every single suggestion. ✌️

Completed

Feature Request: Article/Long-form Content Support in Screenshot API (v1)

Hi team, First off — love the product. I'm a Pro subscriber and have been integrating the screenshot API into my AI agent workflow. Works great for regular tweets. However, I've run into a limitation with X Articles (long-form posts). When I pass an Article tweet ID to GET /api/v1/screenshot/:statusId, the API only returns a minimal card showing the article link — not the full rendered article content with title, body text, and inline images. Interestingly, your web UI handles this perfectly. When I paste the same tweet URL on twittershots.com, the full article renders beautifully with all content blocks and images, and I can export it as a long-form screenshot. So the rendering capability clearly exists — it's just not exposed through the public API. Example tweet: https://x.com/servasyy_ai/status/2042951017462169812 Web UI result: Full article with title, body paragraphs, and embedded images API result: Just a card with a truncated x.com/i/article/2042… link I can see from the network requests that the web UI fetches article data via /api/v2/tweet-details/ (which includes the full contentState with all Draft.js blocks), then renders it client-side. It would be incredibly useful if the v1 screenshot API could also render the full article server-side. My use case: I'm building an AI agent that processes X/Twitter content. For Article-type posts, the current API output is essentially unusable — a simple card with a link has no informational value. The whole reason I subscribed to Pro (300 API calls/month) is to programmatically generate these screenshots. Suggested approach (just a thought): A query parameter like renderArticle=true on the existing endpoint, or A dedicated /api/v1/screenshot/article/:articleId endpoint Would love to hear if this is on the roadmap or if there's a workaround I'm missing. Happy to hop on a quick call if that helps. Thanks for building a great tool! Best, Leon

Professional Leon 3 days ago

2

Planned

Give an option to persist language settings across screenshots

The option to turn on translation for a tweet applies to each tweet individually and needs to be reset if capturing multiple tweets. Twitter has recently made a change to allow automatic translated tweets show on the timeline without translation. Consequently when going back to capture these tweets you have to turn on translation for each individual tweet otherwise the tweet gets captured in the original language.

haloeight 10 days ago

1

Please move color / gradient selection area and/or change behaviour mouseover behaviour

The color / gradient selection area is very close to where the “copy link to tweet” button is. Consequently when switching tabs from twitter to TwitterShots it is very easy for the mouse cursor to go over the color / gradient selection area. And because it changes on mouseover / not requiring a click to select, you can change the background configured by mistake very easily. If the area can be moved from being near to where the copy link to tweet button appears on X and/or change the behaviour of the selection grid so that it’s not just mouseover it would reduce this issue that happens at least several times a day for me. Thanks

haloeight 3 months ago

1

Split tweets - option to set number of tweets per image from a thread

For longer threads (multi-tweet posts) it would be nice to have an option to specify how many tweets to include per image. Right now the “Split Tweets” feature does 1 tweet per image. Depending on the amount of text per tweet it would be valuable to be able to select 2-3 tweets per image as presently to do this kind of consolidation you have to merge the individual split tweets together or copy and split manually a larger 1 image non-split thread.

haloeight 5 months ago

2