XTapDown

Not on the roadmap right now. The toolkit deliberately stays read-only on public data — anything touching your follow graph needs write access to your account, which means OAuth, which means the signup wall I built this to avoid. Export of what the tools already read is a different question and more likely.

Fair concern, and it's the right thing to ask. The honest answer is that it doesn't use a private API — it reads cdn.syndication.twimg.com/tweet-result, the public endpoint that powers embedded tweets across the open web. That's why it's held up: X has a strong incentive not to break embeds, so this surface moves far less than the internal ones. That's not immunity though. It's undocumented, so it can change without notice. What I do instead of pretending otherwise: responses are cached briefly, and every failure maps to an explicit status (notFound / upstream / noMedia) rather than a silent empty result — so when it does break I find out from monitoring, not from users.

Good question. The walk goes upward from the last tweet via in_reply_to_status_id_str. If a parent 404s (deleted or protected), the loop breaks and you get the partial thread — everything from that gap down to the tweet you pasted. No error, no hang, just a shorter result. Anything above the deletion is unrecoverable; the syndication endpoint has no way to reach it. Two other guards in the same loop: a seen-set so a cycle can't spin it, and an author lock — it stops the moment a parent belongs to a different account, so it never wanders out of the self-thread into someone else's replies.

Thanks — no signup was the whole point. The trade is real though: no accounts means no saved history and no idea who's actually using it. Still worth it.

No signup needed for the tools — paste a link and use them. No account, no email, no premium tier. If you meant staying in the loop, there is a newsletter: xtapdown.com/newsletter — that's the only place an email is asked for, and it's optional.

Good question — the split is roughly 6 / 11. Archive & export hygiene: - Tweet Downloader — single tweet or self-thread as PDF, ZIP, offline HTML, Markdown or JSON - Video / GIF / Image downloaders — original quality, no re-encode - Tweet Screenshot — visual capture when you want the rendering, not the data - Advanced Search + operator cheatsheet — finding what you need to capture Day-to-day posting: - Character counter (X-weighted: CJK ×2, URLs 23), thread splitter, hook library, font generator, hashtag library, best-time-to-post, trends, engagement + ad revenue calculators, viral tweet finder Where it stops short of a full archive — and this matters for your use case: 1. It's per-URL, not bulk. There is no "export my account." You paste one tweet at a time. 2. Thread walking only goes upward through your OWN thread. It locks to the first author and stops the moment a parent belongs to someone else, so cross-account conversations aren't captured — only self-threads. 3. Cap is 30 tweets per thread; past that the response is flagged truncated. 4. A deleted or protected tweet mid-thread breaks the walk. You get everything below the gap; anything above it is unrecoverable, because the public syndication endpoint has no path to it. 5. Fields captured are text, timestamp, author, like count and reply count. Not retweet/quote/bookmark counts, not DMs, not your likes or bookmarks. So the honest positioning: it's a scalpel, not an exporter. X's own archive export (Settings → Download an archive) is what gives you the bulk JSON — but that archive is weak exactly where this is strong: media often comes back downscaled or missing, and there's no readable rendering of a thread. That's the gap it fills. On your second question — I genuinely don't know. No signup means no accounts, no analytics on individuals, so I can't see whether anyone is pairing it with a migrator. If you try it alongside one I'd be interested in where it breaks.