What You Can Export from WebSnips
WebSnips is a capture and creation environment, but not every output lives in WebSnips permanently. Articles go to publishing platforms, reports go to Word documents, references go to citation managers, and library backups go to local storage. WebSnips provides export formats for each of these destinations.
The main categories of export:
- Creator Studio drafts — articles, reports, and documents you've written
- Individual clips — the captured content of a specific article or page
- Citations and reference lists — formatted references for captured sources
- Collections — groups of clips with their annotations
- Full library export — your entire WebSnips library for backup or migration
Each category has specific export formats suited to its downstream uses.
Exporting Creator Studio Drafts
Creator Studio is where you write articles, reports, newsletters, and other documents from your research. When a draft is complete, export it to your publishing or editing tool.
How to export a draft:
- Open the draft in Creator Studio
- Click Export in the top toolbar (or use
Cmd+P / Ctrl+P)
- Select the export format
Available draft export formats:
Markdown (.md)
- Best for: Ghost, Substack, Medium (via Markdown import), static site generators (Jekyll, Hugo, Next.js MDX), and any editor that accepts Markdown
- What's included: the full draft text with Markdown formatting (headings, bold, links, lists, code blocks)
- What's not included: images hosted externally (links are preserved); WebSnips-specific formatting that has no Markdown equivalent
- Use this for: blog posts and newsletter content going to any Markdown-native publishing platform
Microsoft Word (.docx)
- Best for: documents going to editors, clients, or colleagues working in Word; reports with formatting requirements
- What's included: formatted text (headings, bold, italic, lists, tables), with styles applied for heading levels
- Use this for: professional reports, policy briefs, business documents that need to pass through a review workflow in Word
HTML (.html)
- Best for: pasting into email marketing platforms (Mailchimp, ConvertKit), CMS editors that accept HTML, or web publishing platforms
- What's included: the full HTML markup of the draft
- Use this for: newsletter HTML going to email platforms
Plain text (.txt)
- Best for: situations where formatting needs to be stripped — pasting into CMS editors that don't handle rich text, basic archiving
- What's included: the text content with no formatting markup
- Use this for: CMS platforms with their own formatting tools where Markdown or HTML would appear as raw markup
PDF (.pdf)
- Best for: sharing a formatted, final version of a document that shouldn't be editable
- What's included: the draft rendered as a formatted PDF document
- Use this for: client deliverables, formal reports, documents that need to look polished without being editable
Copying to clipboard:
For quick paste to any destination, the Copy button in Creator Studio copies the draft text in the format best suited to the target editor (usually rich text or Markdown, depending on the platform detected).
Exporting Individual Clips
An individual clip's export downloads the content of that specific captured article or page.
How to export a clip:
- Open a clip from your library
- Click the Export (download) icon in the clip detail header
- Select the export format
Available clip export formats:
Markdown (.md)
- Exports: the captured article text formatted as Markdown, with your annotation notes appended at the bottom
- Use for: saving a captured article as a portable file, incorporating into a Markdown-based knowledge base (Obsidian, Logseq)
HTML (.html)
- Exports: the captured HTML content of the page
- Use for: exact recreation of the captured article in an HTML viewer
Plain text (.txt)
- Exports: the full text of the captured article without markup
- Use for: text analysis, bulk processing
Clip metadata (JSON)
- Exports: the full clip metadata: title, URL, author, date, tags, Collections, annotation notes, highlights, citation data — as a JSON file
- Use for: developer integrations, data analysis, migration to other tools
What's included in a clip export:
- The captured article text
- Your annotation notes (in Markdown and HTML exports)
- Your highlights (marked in the exported text)
- Citation metadata (available in JSON export)
What's not included:
- Images from the original page (these are usually hosted on the source site and not captured)
- Comments or replies from the original page
- Dynamic or JavaScript-rendered content that wasn't captured at save time
Exporting Collections
A Collection export downloads multiple clips — all the clips in a Collection — in bulk.
How to export a Collection:
- Open a Collection
- Click the Settings (gear) icon in the Collection header, or the Export option in the Collection menu
- Select the export format and options
Available Collection export formats:
Markdown archive (.zip)
- Exports: a ZIP file containing one
.md file per clip, with clip annotation notes appended
- What's included: each clip's full text, your annotation, highlights
- Use for: backing up a research Collection; importing into Obsidian (place the .md files in an Obsidian vault folder)
CSV with metadata
- Exports: a CSV file with one row per clip, columns for title, URL, author, date, tags, Collections, annotation notes, first 500 characters of body text
- What's included: metadata for all clips in the Collection
- Use for: spreadsheet-based analysis, sharing a source list with collaborators, data processing
JSON data export
- Exports: a JSON array with the full data for each clip (all fields)
- Use for: technical integrations, migration, analysis
Citation list export (see next section)
Export options:
When exporting a Collection, select:
- Include clips: all clips, or only clips with a specific tag (e.g., only
rp-to-cite clips)
- Include annotations: yes/no — if sharing with someone who doesn't need your private notes, deselect
- Include highlights: yes/no
- File per clip vs. single file: for Markdown export, one file per clip (for Obsidian) vs. all clips in a single concatenated file
Exporting Citation Lists
Citation list export is designed specifically for academic and professional writing that requires properly formatted references.
How to export citations:
From a single clip:
- Open the clip
- Open the Citation panel
- Select the citation style
- Click Copy Citation (single citation to clipboard) or Export (download as a file)
From a Collection:
- Open the Collection
- Click Export Citations in the Collection header
- Select:
- Citation style (APA, MLA, Chicago Author-Date, Chicago Notes-Bibliography, Harvard, Vancouver, IEEE)
- Which clips to include (all clips, or only
rp-to-cite tagged clips)
- Click Export
Available citation export formats:
Formatted reference list (.txt or .docx)
- Exports: a properly formatted reference list in the selected citation style, ready to paste into a document
- One entry per clip, alphabetically sorted (or by citation order for numbered styles)
BibTeX (.bib)
- Exports: citation data in BibTeX format
- Use for: Zotero, Mendeley, LaTeX-based academic writing
RIS (.ris)
- Exports: citation data in RIS format
- Use for: Mendeley, EndNOTE, Zotero, and most citation managers
JSON-LD
- Exports: machine-readable citation data in JSON-LD format
- Use for: developer integrations
Importing citation exports into Zotero:
- Export from WebSnips as BibTeX or RIS
- In Zotero: File → Import → select the exported file
- The citations appear in Zotero's library with all available fields (title, author, date, URL, journal)
- Review imported entries for completeness — some fields (volume, issue, pages) may be missing if they weren't extractable from the web page
Full Library Export
A full library export downloads your entire WebSnips library — all clips, annotations, highlights, Collection structure, tags, and metadata — for backup or migration purposes.
How to export your full library:
- Settings → Import & Export → Export Library
- Select the export format
- Click Export — the export file is generated and downloads
Available full library export formats:
WebSnips Archive (.wsarchive)
- Exports: proprietary WebSnips format containing complete library data including all clip text, annotations, highlights, Collections, tags, Connections data, and settings
- Use for: backup (importable back into WebSnips); complete account restoration
- Recommended cadence: monthly backup
JSON export (.json)
- Exports: all library data as a structured JSON file
- Use for: data portability, migration to other tools, developer analysis
- Note: images and some dynamic content are not included
Markdown archive (.zip)
- Exports: one Markdown file per clip, organized into folders by Collection structure
- Use for: migration to Obsidian or other Markdown-based knowledge bases
- Limitations: Connections data (links between clips) is not represented in Markdown format; Collection structure is preserved as folder hierarchy
What's included in a full library export:
- All clips (full captured text)
- All annotations and highlights
- All tags and Collection assignments
- Collection structure and names
- Connections data (in JSON and .wsarchive formats)
- Settings (in .wsarchive format)
What's not included:
- Images (these remain on their original hosting servers)
- AI-generated content that wasn't saved explicitly
- Account credentials
Worked Example: A Content Strategist's Export Workflow
Setup: A content strategist uses WebSnips to research and draft client deliverables — content strategy documents, editorial calendars, and sample articles. Each deliverable has a different downstream workflow.
Deliverable 1: Client strategy report (Word format)
She researches with WebSnips, drafts in Creator Studio, and the client expects a Word document:
- Draft in Creator Studio
- Export as .docx
- Apply the client's Word template (styles, logo) in Word
- Send for review
Deliverable 2: Blog article for publication (Markdown format)
Researched and drafted in WebSnips, published to the client's Next.js blog:
- Draft in Creator Studio
- Export as .md
- Paste into the CMS or commit to the blog source repo
- The Markdown renders correctly in the publishing platform
Deliverable 3: Newsletter issue (HTML format)
Newsletter content drafted in Creator Studio, sent via Mailchimp:
- Draft in Creator Studio (Thread mode for subject line variations, full article mode for the newsletter body)
- Export as HTML
- Paste into Mailchimp's HTML editor
- Review rendering, adjust if needed
Deliverable 4: Research source list for client (Citation export)
Client wants a formatted reference list of the 22 sources used in the strategy report:
- Tag all cited sources
rp-to-cite during the research phase
- Export Citations from the project Collection → APA style → .docx
- Copy formatted reference list into the strategy report's appendix
Deliverable 5: Monthly library backup
Every month on the first:
- Settings → Export Library → WebSnips Archive (.wsarchive)
- Save to Dropbox with filename
websnips-backup-YYYY-MM.wsarchive
This preserves the complete library state in case of account issues or migration.
Key Takeaways
- Creator Studio drafts export in Markdown, Word, HTML, PDF, and plain text: match the export format to the downstream tool — Markdown for publishing platforms, Word for professional review, HTML for email platforms, PDF for polished client deliverables.
- Individual clip exports include captured text, your annotations, and highlights: useful for incorporating specific researched sources into external knowledge bases (Obsidian) or text analysis workflows.
- Collection CSV export is the fastest way to share a source list: one row per clip with title, URL, annotation, and tags — shareable with collaborators who don't use WebSnips.
- Citation list export in BibTeX or RIS integrates directly with Zotero and Mendeley: citations captured in WebSnips are portable to citation management software without manual re-entry.
- Monthly .wsarchive library backups protect your complete knowledge base: WebSnips archives are the only format that includes Connections data and can be restored to a WebSnips account.
Conclusion
WebSnips' export capabilities are designed for the full range of downstream uses: publishing platforms expect Markdown, editors expect Word, email platforms expect HTML, academic writing requires citation formats, and backup storage needs portable archives. Understanding which export format fits each use case eliminates the manual reformatting step — the draft, reference list, or data that leaves WebSnips arrives at its destination ready to use. For users who work across multiple tools (as most professionals do), this portability is what makes WebSnips viable as the central research and drafting environment rather than one tool among many siloed alternatives.
Export your next Creator Studio draft in the format your publishing platform needs — no reformatting, no copy-paste friction, just the content where you need it.