Skip to main content
Exporting your argument analysis allows you to save results for future reference, share with others, or integrate with other tools.

Available Export Options

Currently, you can export analysis data in several ways:

JSON Export

Complete structured data in JSON format

Copy to Clipboard

Quick copy of analysis sections

Manual Screenshot

Visual capture of argument maps

Exporting JSON Data

The most comprehensive export format includes all analysis components.

What’s Included in JSON Export

Argument Blueprint

Complete array of all argument nodes:
{
  "blueprint": [
    {
      "id": "thesis-1",
      "parentId": null,
      "type": "thesis",
      "side": "for",
      "content": "Universal basic income should be implemented",
      "sourceText": "...",
      "source": "Topic query",
      "fallacies": [],
      "logicalRole": "Main proposition"
    },
    // ... more nodes
  ]
}
Includes all nodes with their complete metadata, relationships, and fallacy annotations.

How to Export JSON

1

Complete your analysis

Wait for the analysis to finish and results to appear on screen.
2

Open browser console

  • Chrome/Edge: Press F12 or Ctrl+Shift+I (Windows) / Cmd+Option+I (Mac)
  • Firefox: Press F12 or Ctrl+Shift+K
  • Safari: Enable Developer menu first, then press Cmd+Option+I
3

Access the data

The analysis results are available in the page’s JavaScript context. You can:
  • Inspect the network response containing the results
  • Use browser DevTools to extract the data object
  • Copy the entire analysis from the network tab
4

Save to file

Copy the JSON data and save it to a .json file using any text editor.
This method requires technical familiarity with browser developer tools. A built-in export button may be added in future versions.

Copying Text Content

For quick sharing or note-taking, you can copy specific sections:

Copy Summary

1

Locate the summary section

Find the summary text in your analysis results.
2

Select the text

Click and drag to highlight the summary content.
3

Copy to clipboard

  • Windows/Linux: Ctrl+C
  • Mac: Cmd+C
4

Paste elsewhere

Use Ctrl+V (or Cmd+V) to paste into documents, emails, or notes.

Copy Analysis Text

Follow the same process for the detailed analysis section to extract the qualitative insights.

Copy Individual Arguments

You can also copy specific arguments or nodes from the blueprint visualization:
  1. Identify the argument node you want to copy
  2. Select the text content
  3. Copy using keyboard shortcuts
  4. Paste into your preferred format
When copying arguments, include the node type, side, and any fallacy annotations for complete context.

Visual Export (Screenshots)

For presentations or visual documentation:

Taking Screenshots

Windows Screenshot Methods

Full Screen:
  • Press PrtScn to copy entire screen to clipboard
  • Press Win+PrtScn to save screenshot to Pictures folder
Partial Screen:
  • Press Win+Shift+S to open Snipping Tool
  • Select the area you want to capture
  • Screenshot is copied to clipboard
Third-party tools:
  • ShareX (free, open-source)
  • Greenshot (free)
  • Snagit (paid)

Best Practices for Screenshots

Capture Complete Sections

Ensure entire argument trees are visible before capturing

High Resolution

Use high DPI settings for clear text in presentations

Annotation

Use annotation tools to highlight key arguments or fallacies

Consistent Styling

Keep browser zoom at 100% for consistent screenshots

Exporting from History

Currently, there is no direct export functionality from the History page. You must export data immediately after analysis.

Workaround

To export an analysis from your history:
1

Access history

Navigate to the History page and locate your analysis.
2

Note the input

Remember or copy the original topic/URL/document.
3

Re-run analysis

Create a new analysis with the same input.
4

Export immediately

Use one of the export methods while viewing the fresh results.
This limitation will be addressed in future updates with direct export from history.

Data Structure for Integration

If you’re integrating exported data with other tools, here’s the complete type structure:

TypeScript Definitions

type ArgumentNode = {
  id: string;
  parentId: string | null;
  type: 'thesis' | 'claim' | 'counterclaim' | 'evidence';
  side: 'for' | 'against';
  content: string;
  sourceText: string;
  source: string;
  fallacies: string[];
  logicalRole: string;
};

type Tweet = {
  id: string;
  text: string;
  author: {
    name: string;
    username: string;
    profile_image_url: string;
  };
  public_metrics: {
    retweet_count: number;
    reply_count: number;
    like_count: number;
    impression_count: number;
  };
  created_at: string;
};

type AnalysisResult = {
  blueprint: ArgumentNode[];
  summary: string;
  analysis: string;
  socialPulse: string;
  tweets: Tweet[];
};

Parsing JSON Exports

// Read the JSON file
const fs = require('fs');
const analysisData = JSON.parse(
  fs.readFileSync('analysis.json', 'utf8')
);

// Access components
const blueprint = analysisData.blueprint;
const summary = analysisData.summary;
const tweets = analysisData.tweets;

// Find thesis
const thesis = blueprint.find(
  node => node.type === 'thesis' && node.parentId === null
);

// Filter by node type
const claims = blueprint.filter(node => node.type === 'claim');
const evidence = blueprint.filter(node => node.type === 'evidence');

// Find nodes with fallacies
const fallacious = blueprint.filter(
  node => node.fallacies.length > 0
);

Use Cases for Exported Data

Research

Analyze argument patterns across multiple debates

Education

Teach critical thinking and logical analysis

Documentation

Create reference materials for decision-making

Presentations

Incorporate argument maps into slides and reports

Comparison

Compare argument structures across different sources

Visualization

Build custom visualizations of argument trees

Archiving

Preserve analyses for long-term reference

Collaboration

Share with colleagues for joint review

Sharing Exported Data

Email

1

Export to JSON

Save your analysis as a .json file.
2

Attach to email

Add the JSON file as an attachment.
3

Include context

Explain what the analysis covers and how to interpret it.
4

Consider screenshots

Attach visual exports for recipients who prefer visual formats.

Cloud Storage

Upload exported files to:
  • Google Drive
  • Dropbox
  • OneDrive
  • GitHub (for version control)

Collaboration Platforms

Share via:
  • Slack (upload files to channels)
  • Microsoft Teams (attach to conversations)
  • Notion (embed or link)
  • Confluence (attach to pages)
When sharing JSON data, provide a brief guide on the data structure so recipients understand the format.

Future Export Features

Planned enhancements:
  • One-click JSON export button: Download with a single click
  • PDF export: Generate formatted PDF reports
  • CSV export: Export blueprint as spreadsheet data
  • Markdown export: Generate markdown-formatted summaries
  • PNG/SVG export: Export argument tree visualizations
  • Batch export: Export multiple analyses from history at once
  • Custom export templates: Choose which sections to include
  • Direct sharing: Share via link without manual export

Troubleshooting

The analysis data is available in the network response:
  1. Open DevTools Network tab before running analysis
  2. Run your analysis
  3. Look for the API request in the network log
  4. Click on the request and view the Response tab
  5. Copy the JSON data from there
If your exported JSON won’t parse:
  • Ensure you copied the complete JSON object
  • Check for missing brackets or quotes
  • Use a JSON validator (jsonlint.com) to identify syntax errors
  • Verify there are no truncated values
To improve screenshot quality:
  • Increase your display resolution
  • Use browser’s built-in screenshot tools (higher quality)
  • Set browser zoom to 100% before capturing
  • Use dedicated screenshot tools with quality settings
If tweet data is missing:
  • Social Pulse may not have been available for your topic
  • API credentials may not be configured
  • The search may not have returned results
This doesn’t affect the argument blueprint or analysis sections.

Build docs developers (and LLMs) love