Twitter to Video features, what you really need?

We’re exploring video features for TwitterShots 🎬 If you could turn a Tweet or thread into a video, what would be most useful to you? A few ideas we’re considering: Tweet → animated video Thread → slideshow video Tweet → Reel / TikTok / Shorts Tweet → GIF Tweet + AI → UGC faceless video What would you actually use? Vote for the features you want most, or leave a comment with anything we missed.

Create login account

I was told no login required. Then a login screen appeared. Then no apparent way to create login account. Then found create account on feedback screen. That whole process sucks.

Export Image doesn't do anything on iOS

What the subject says, hitting export offers a download window to “view” or “download” the image, then doesn’t view or save anything. Tried it on both iPad and phone and it does the same thing.

Replies are not captured the same in the bulk interface as in the main interface

In the main interface if you paste the link to a replace it will capture the parent tweet as well correctly as part of a thread (or split up if that option is set). In the bulk interface it only captures the reply omitting the parent.

Consider naming bulk captured screenshots and one offs with the same conventions

At present the screenshots captured via bulk are named differently / numerically than those done one off (including account name and some identifier). Having the two naming conventions match would prevent duplicates.

Consider implementing translation like Twitter

Currently the translated text is placed below the original text doubling the size of the screenshot. This must be manually edited out if you just want to post one language e.g. that of your audience. On Twitter the automatic translations apply to the reader’s settings. As well, consider using a different translation service as the current one does not produce the same translations at Twitter, often times incorrect.

Bulk capture does not work correctly

When capturing tweets by bulk capture, long tweets are being cut off instead of being captured in full as they are done when capturing tweets individually. The screenshots must then be redone manually.

Threaded posts are no longer being captured correctly

The last tweet in a thread is just captured and not any of the tweets that precede it

Rate restriction lockout + speed to screen shot = unusable

Please fix this along with the rate restrictions. 2 screenshots every ten minutes is unusable. It takes 10 seconds per screenshot and then if you try capturing anything faster than this you are locked out for 600 seconds. The timer doesn’t refresh automatically so if you hit refresh on the screen to see how many seconds remain on the lockout, it starts over again. This is really bad.

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

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.

Problem with split threads

The first item in a thread is being copied twice into the resulting zip file while missing the last item in a thread.

Speed of output has gotten bad

Sometimes takes around 8-10 seconds to get a screenshot.

Add ability to adjust width of pictures / words per line

The aspect ratio controls don’t really change the width of the pictures or amount of text per line. Some screenshots heavily in text come out very long and narrow, when it would be more readable to have the text spread a bit wider first.

Screenshots are completely broken

All output is coming out with pictures missing, broken formatting, text cut off, white space added

Something has broken with threaded tweets

Everything but the last tweet in a thread is captured while the rest of the entries are empty.

Fix the text pricing

Please set the 4:5 aspect ratio to output at 1080x1350

Please consider making the 4:5 aspect ratio generate tweets at 1080 x 1350 pixels, instead of 996 × 1xxx pixels, to ensure maximum quality and compatibility with Instagram. Thank you very much.

Add keyboard shortcut for split tweets toggle

Please consider adding a keyboard shortcut for this. Thanks

Please move the Split Tweets controls higher on the page

Currently you have to scroll down to access it and it is one of the features that is switched on or off quite frequently