Export & File Management

TL;DR

Save your projects to Dashboard, export content in multiple formats (Markdown, text, PDF), and manage configurations as reusable templates. Keep your work organized and accessible.

Save Output to Dashboard

Preserve your complete project including all generated content, inputs, and analysis for future reference.

What Gets Saved:

  • • All generated output cards (originals, alternatives, voice styles, modifications)
  • • All form inputs used for generation
  • • Comparison results if you ran "Compare All Outputs"
  • • Relationships between outputs (which are alternatives, which are derived versions)
  • • Metadata (generation date, AI model used, word counts, scores)

When to Use:

  • • Finished generating and want to preserve everything
  • • Need to reference this project later
  • • Want to show outputs to team members
  • • Need version history across iterations
  • • Before closing browser to avoid losing work

How to Access Saved Projects:

  1. 1. Go to Dashboard from main navigation
  2. 2. Click "Saved Outputs" tab
  3. 3. Browse by date or project name
  4. 4. Click any saved output to restore everything exactly as saved

Understanding Copy Sessions vs Saved Outputs

CopyZap uses a two-tier storage system to keep your workspace clean while preserving important work.

Copy Sessions (Auto-Save / Temporary)

What: Every time you click "Generate," your input settings only are automatically saved as a session (form configuration, prompts, parameters)

What's NOT saved: Generated outputs/content are NOT stored in sessions

Purpose: Lets you quickly restore your input settings and parameters without preserving the actual generated content

Lifecycle: Temporary - automatically cleaned up to prevent database bloat

Retention Policy:

  • • Sessions older than 30 days are automatically deleted
  • • Each user is limited to their 50 most recent sessions
  • • Cleanup runs daily at 2 AM UTC

User control: You never have to manage these - they're automatic

Example: You generate 20 different versions of an email this week → all input settings auto-saved as sessions (but NOT the generated emails) → after 30 days, they're gone unless you explicitly saved your favorites

Saved Outputs (Permanent Storage)

What: When you click "Save Output" button, both your inputs AND generated outputs are marked for permanent storage

Purpose: Long-term preservation of important work you want to keep

Lifecycle: Permanent - never automatically deleted

Features:

  • • Add custom title and description
  • • Tag for easy searching
  • • Organize by project or client
  • • Load back anytime to continue editing

User control: You decide what to save and when to delete

Example: You love version 3 of your email → click "Save Output" → it's preserved forever in your Saved Outputs library

Why Two Systems?

Without this approach:

  • ❌ Save everything forever → Database fills with junk
  • ❌ Delete old work → Users lose important projects

With this system:

  • ✅ Working sessions are temporary (like browser history)
  • ✅ Important work is preserved (like bookmarks)
  • ✅ Database stays clean and fast
  • ✅ You never lose what matters

Workflow Example:

  1. 1. Monday: Generate 10 blog headline variations → all input settings auto-saved as sessions (but NOT the generated headlines)
  2. 2. Tuesday: Love headline #7 → click "Save Output" → inputs AND outputs saved to Saved Outputs
  3. 3. 45 days later: The 10 auto-saved sessions → deleted automatically (over 30 days old)
  4. 4. 45 days later: Your saved headline #7 → still in Saved Outputs with full content, ready to use

Key Takeaway:

  • Don't worry about sessions - they're automatic working copies
  • Do use "Save Output" for any work you want to keep long-term
  • Think of it like Google Docs: Auto-save handles drafts, you star/bookmark what matters

Export Formats

Export your content in multiple formats for different use cases and tools.

Copy as Markdown

Copies all generated content to clipboard in Markdown format for easy pasting into documentation tools.

What's Included:

  • • Project inputs summary
  • • All generated output versions
  • • Scores if generated
  • • Comparison results if run
  • • Proper Markdown formatting (headers, lists, emphasis)

Format Example:

# Copy Generation Project
**Project Description:** Landing page for meal delivery service
**Target Audience:** Busy professionals

## Improved Copy
Tired of choosing between healthy eating and saving time?
FreshMeals delivers chef-prepared, nutritious meals...

**Word Count:** 156 words

## Alternative Copy
Your lunch break shouldn't be a compromise...

**Word Count:** 142 words

When to Use:

  • • Documenting your work
  • • Sharing with team via Slack/email
  • • Saving to Notion, Obsidian, or other Markdown tools
  • • Creating project archives
  • • Writing reports or case studies
  • • Version control (Git)

Export to Text

Downloads everything as a plain .txt file with automatic naming.

Filename Format:

[project-description]_[date-time].txt

Example: meal-delivery-landing_2025-11-10_14-30-22.txt

What's Included:

  • • Same content as Markdown export
  • • Plain text formatting (no special syntax)
  • • All outputs and metadata
  • • Opens in any text editor

When to Use:

  • • Need offline access
  • • Sharing with clients who want simple format
  • • Archiving projects long-term
  • • Working in tools without Markdown support
  • • Simple backup copies

Export to PDF

Generates a professionally formatted PDF document with all your content.

PDF Includes:

  • • Professional formatting and layout
  • • Clear section divisions and headers
  • • All generated outputs with labels
  • • Metadata and scores
  • • Comparison results if available
  • • Print-friendly formatting

When to Use:

  • • Presenting to clients
  • • Formal documentation
  • • Stakeholder review and approval
  • • Portfolio pieces
  • • Print-friendly version needed
  • • Email attachments for formal sharing

Copy Individual Outputs

Each output card has THREE copy options: Copy (plain text), Copy HTML (clean HTML), and Copy MD (full markdown with metadata).

Copy (Plain Text)

Standard copy button that copies only the main copy content as plain text.

What's Copied:

  • Only the copy content (no scores, no metadata)
  • • Preserves line breaks and paragraph structure
  • • Strips markdown formatting
  • • Perfect for pasting directly into your CMS or document
  • • Visual confirmation when copied

Copy HTML (Clean HTML)

Copies only the main copy content formatted as clean, semantic HTML.

What's Copied:

  • Only the copy content as HTML (no scores, no metadata)
  • • Proper HTML tags (h1, h2, p, ul, li, etc.)
  • • Ready to paste into HTML editors
  • • Clean markup without inline styles
  • • Perfect for WordPress, Webflow, or any HTML-based CMS

Copy MD (Full Markdown)

UPDATED

Copies the entire output card including all sections, scores, and metadata in comprehensive markdown format.

Button Location:

  • • Top-right corner of each output card
  • • Icon shows "MD" with code symbol
  • • Tooltip: "Copy content in markdown format"
  • • One-click operation

What's Included:

  • • Card title with persona/brand voice info
  • • Full copy content in Markdown format
  • • Quality scores and explanations
  • • GEO scores and breakdown
  • • SEO metadata (URL slugs, meta descriptions, headings)
  • • FAQ Schema (if generated)
  • • Modification instructions (if applied)
  • • All sections formatted as proper markdown

Perfect For:

  • • Archiving complete output with all analytics
  • • Sharing detailed results with team members
  • • Documentation and reporting
  • • Pasting into Notion, Obsidian, or Confluence
  • • Adding to GitHub/GitLab for version control
  • • Client presentations with full details

Pro Tip: Use "Copy" or "Copy HTML" when you just need the content. Use "Copy MD" when you need the complete record with all metadata and scores.

Configuration Management

Save and reuse form configurations for consistent, efficient content creation.

Export / Import JSON

Save your form configuration as a JSON file or load one from disk.

Export JSON:

  • • Downloads current form state as .json file
  • • Includes all settings and inputs
  • • Does NOT include generated outputs
  • • Automatic filename based on project

Import JSON:

  • • Upload a previously exported .json file
  • • Instantly restores all form fields
  • • Overwrites current form state
  • • Warning prompt before overwriting

Backup Configurations

Save complex setups before experimenting. Create backups before major changes.

Share with Team

Export your configuration and share the file with colleagues. They import to get identical setup.

Version Control

Save different versions of similar projects. Compare approaches side-by-side.

Cross-Project Consistency

Use same setup across multiple pieces. Ensure brand consistency. Standardize team processes.

Save as Template

Save your current form configuration as a reusable template in the app.

How It Works:

  1. 1. Configure your form with desired settings
  2. 2. Click "Save as Template"
  3. 3. Enter a descriptive name
  4. 4. Template saved to your account
  5. 5. Access from "Load Template" dropdown anytime

Common Template Use Cases:

  • • Product page template with brand voice presets
  • • Email campaign template with tone settings
  • • Blog post intro template with SEO settings
  • • Social media post template with character limits
  • • Landing page hero template with structure presets

Time Saver: Templates save 5-10 minutes per project by eliminating repetitive setup work.

Organize Your Work

Naming Best Practices

  • • Use descriptive project names: "Product-Landing-Hero-v2" not "Copy1"
  • • Include version numbers for iterations
  • • Add dates for time-sensitive projects
  • • Use consistent naming conventions across team
  • • Include client name or project code if applicable

File Organization Tips

  • • Create folders for exported files by client or project
  • • Keep JSON configs separate from content exports
  • • Archive completed projects after use
  • • Document what each template is for
  • • Regular cleanup of old exports and configs

Best Practices

Save to Dashboard before closing browser - avoid losing work

Export JSON configs for recurring content types - saves setup time

Use Markdown export for documentation and team sharing

Use PDF export for client presentations and formal deliverables

Create templates for content you produce regularly - product pages, emails, social posts

Name files descriptively - helps future you find projects quickly

Related Pages

Was this helpful?