Twitter Data & Export Suite
Convert Twitter and X posts and conversations into machine-readable datasets, personal knowledge vault notes, vector print documents, and offline digital archives.
Data Science (6)
Structured data & programmatic ingestionTweet to JSON
Normalized single-post JSON schema with 64-bit Snowflake string shielding.
Twitter Thread to JSON
Sequential thread array with parent-child reply IDs for LLM and RAG pipelines.
Tweet to CSV
Clean tabular row formatted for Excel, Google Sheets, and SQL databases.
Twitter Thread to CSV
Hierarchical thread dataset with chronological position indexing and reply tracking.
Tweet to RSS
Portable one-post RSS feed snapshot with CDATA escaping and GUID permalinks.
Twitter Thread to RSS
Multi-item chronological feed channel with media enclosures for feed aggregators.
PKM & Notes (4)
Obsidian, Notion & plain text pipelinesTweet to Markdown
Obsidian and Notion-ready markdown with standardized YAML frontmatter metadata.
Twitter Thread to Markdown
Connected long-form essay layout with numbered chapter subheadings and photo embeds.
Tweet to TXT
Normalized plain text with t.co short links stripped and whitespace compacted.
Twitter Thread to TXT
Chronological narrative text dump for terminal pipes, speech synthesis, and local grep.
Publishing & Reading (6)
Printable PDFs, ebooks & reading viewsTweet to PDF
Print-ready vector PDF formatted with CSS Paged Media rules and 300 DPI photos.
Twitter Thread to PDF
Seamless multi-post book format preventing awkward page splits across tweet cards.
Tweet to HTML
Zero-dependency, self-contained HTML snapshot with inline CSS styles.
Twitter Thread to HTML
Offline reader timeline with responsive dark mode and vertical connector lines.
Twitter Thread to EPUB
Reflowable ebook container with TOC navigation, compatible with Kindle and Apple Books.
Twitter Thread Reader
Distraction-free web reading view that unrolls long threads into a continuous article.
Archival (3)
Offline bundles & batch processingTwitter Thread Archive
Digital preservation package containing Markdown, HTML, JSON manifest, and localized media.
Twitter Thread Downloader
Quick multi-format hub to download thread text as TXT, Markdown, or JSON.
Batch Tweet Downloader
Process up to 5 public post links simultaneously with separate error handling.
Engineering specifications: Data integrity & encoding standards
Converting dynamic social graph data into permanent file formats presents unique engineering challenges. TwiFlux adheres to strict specifications across all export routes:
- Snowflake ID Float Protection: Modern Twitter status IDs are 64-bit unsigned integers. Because standard JavaScript numbers lose precision past $2^53-1$, TwiFlux guarantees that all IDs are serialized and shielded as strings (
id_str). - RFC 4180 CSV Escaping: Tweet bodies with embedded line breaks, quotation marks, or commas are properly enclosed in double quotes with internal quotes escaped as
"". - CSS Paged Media Standards: PDF exports implement
@pagedeclarations andbreak-inside: avoidrules to guarantee clean sheet margins on A4 and US Letter sizes. - Standardized PKM Frontmatter: Markdown files output YAML frontmatter parseable by Obsidian Dataview, Notion, and Logseq.
Single Tweet vs. Multi-Post Thread: Choosing the right export
Selecting the appropriate tool depends on whether you are analyzing an individual post or preserving an extended narrative:
Use Single Tweet Converters when creating atomic citations, saving standalone quotes, or embedding individual tweets into spreadsheets.
Use Thread Converters when archiving multi-post tutorials, serialized essays, or complex discussions where chronological sequence and reply structure are critical.
Frequently Asked Questions
How does TwiFlux choose between Single Tweet and Thread tools?
Single Tweet tools extract only the specific post requested, optimizing for speed and atomic records. Thread tools trace the parent-child conversation hierarchy upward to the root tweet and downward through replies to deliver a complete chronological story.
Why do CSV and JSON exports keep Snowflake IDs as strings?
JavaScript and spreadsheet applications represent numbers using 64-bit floating point (IEEE 754), which truncates integers above 9,007,199,254,740,991. Because modern Twitter Snowflake IDs are 19 digits long, storing them as strings prevents silent data corruption.
Can I use the exported Markdown files directly in Obsidian or Notion?
Yes. All Markdown exports include standardized YAML frontmatter properties (title, author, source, id, date, tags). Obsidian Dataview, Notion database imports, and Logseq immediately parse these fields as native properties.
Are these exports generated in the cloud or in my browser?
All document generation (PDF synthesis, HTML bundling, EPUB packaging, and ZIP compression) is executed client-side in your browser using modern Web Workers. Your data is not stored or shared.
Explore more topic clusters
Need media extraction? Visit our Twitter Media Downloader Suite or explore writing utilities in the Twitter Creator Suite.