Skip to content
Skills Library
Marketing & content · Conversion & formats

format-export

/format-export

This skill provides screenplay export procedures for PDF, FDX, and HTML. Covers Better Fountain VS Code extension, afterwriting CLI, and Highland for converting Fountain files to industry-standard delivery formats. Use when: exporting screenplay to PDF, converting to Final Draft (FDX), generating HTML preview, or preparing scripts for delivery.

Licence
MIT
Last repository change
05.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 05.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

This skill provides screenplay export procedures for PDF, FDX, and HTML. Covers Better Fountain VS Code extension, afterwriting CLI, and Highland for converting Fountain files to industry-standard delivery formats. Use when: exporting screenplay to PDF, converting to Final Draft (FDX), generating HTML preview, or preparing scripts for delivery.

Original author description

This skill provides screenplay export procedures for PDF, FDX, and HTML. Covers Better Fountain VS Code extension, afterwriting CLI, and Highland for converting Fountain files to industry-standard delivery formats. Use when: exporting screenplay to PDF, converting to Final Draft (FDX), generating HTML preview, or preparing scripts for delivery.

How it works

  1. Invocation Triggers
  2. Recommended: Better Fountain Extension
  3. Export Formats Overview
  4. PDF Export
  5. FDX Export (Final Draft XML)
  6. HTML Export
  7. Export Workflow
  8. Version Naming
  9. Troubleshooting
  10. Export Checklist
Original SKILL.md headings · 206 lines, 772 words
SKILL.md preview
---
name: format-export
description: |
  This skill provides screenplay export procedures for PDF, FDX, and HTML.
  Covers Better Fountain VS Code extension, afterwriting CLI, and Highland
  for converting Fountain files to industry-standard delivery formats.

  Use when: exporting screenplay to PDF, converting to Final Draft (FDX),
  generating HTML preview, or preparing scripts for delivery.
---

# Format Export Skill

## Invocation Triggers
Apply this skill when:
- Exporting screenplay to PDF
- Converting to Final Draft (FDX)
- Generating HTML preview
- Preparing scripts for delivery

## Recommended: Better Fountain Extension

The simplest export method uses the [Better Fountain](https://marketplace.visualstudio.com/items?itemName=piersdeseilligny.betterfountain) VS Code extension:

| Format | Command Palette Action |
|--------|------------------------|
| PDF | `Fountain: Export to PDF` |
| FDX | `Fountain: Export to FDX` |
| HTML | `Fountain: Export to HTML` |

**Steps:**
1. Open `.fountain` file in VS Code
2. Press `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS)
3. Type the export command
4. Choose output location

## Export Formats Overview

| Format | Extension | Purpose | Tools |
|--------|-----------|---------|-------|
| PDF | .pdf | Industry standard delivery | Better Fountain, afterwriting, Highland |
| FDX | .fdx | Final Draft import | Better Fountain, screenplain, Highland |
| HTML | .html | Web preview/sharing | Better Fountain, afterwriting |
| Plain Text | .txt | Accessibility, archival | direct copy |

## PDF Export

### Industry Standard Format
- **Font:** Courier 12pt
- **Margins:** 1.5" left, 1" right, 1" top/bottom
- **Page Size:** US Letter (8.5" x 11")
- **Page Numbers:** Top right, starting page 2

### Better Fountain (Recommended)
In VS Code: `Ctrl+Shift+P` -> "Fountain: Export to PDF"

### CLI: afterwriting (for automation)
```bash
# Install
npm install -g afterwriting

# Basic PDF export
afterwriting --source screenplay.fountain --pdf

# With configuration
afterwriting --source screenplay.fountain --pdf --config pdf-config.json

# Output to specific file
afterwriting --source screenplay.fountain --pdf --output script.pdf
```

### PDF Configuration (pdf-config.json)
```json
{
  "print_title_page": true,
  "print_profile": "default",
  "print_header": "",
  "print_footer": "",
  "print_watermark": "",
  "print_dialogue_numbers": false,
  "print_notes": false,
  "print_sections": false,
  "print_synopses": false,
  "scenes_numbers": "none",
  "each_scene_on_new_page": false
}
```

## FDX Export (Final Draft XML)

### Purpose
- Import into Final Draft software
- Collaboration with Final Draft users
- Industry compatibility

### Better Fountain (Recommended)
In VS Code: `Ctrl+Shift+P` -> "Fountain: Export to FDX"

### CLI: screenplain (for automation)
```bash
# One-time installation (requires Python 3.8+ and pipx)
pipx install screenplain

# Export to FDX
screenplain --format fdx screenplay.fountain output.fdx
```

## HTML Export

### Purpose
- Web-based reading
- Easy sharing via URL
- Print from browser

### Better Fountain (Recommended)
In VS Code: `Ctrl+Shift+P` -> "Fountain: Export to HTML"

### CLI: afterwriting (for automation)
```bash
afterwriting --source screenplay.fountain --html
```

## Export Workflow

### Pre-Export Checklist
- [ ] Script Supervisor approval
- [ ] Standards Reviewer approval
- [ ] All [[notes]] resolved or intentional
- [ ] Title page complete and current
- [ ] Fountain syntax validated

### Export Process
```markdown
1. Validate Fountain file
2. Run export command
3. Verify output file created
4. Open and review output
5. Check page count
6. Verify title page
7. Sample check formatting
8. Package for delivery
```

### Post-Export Verification
- [ ] File opens without errors
- [ ] Page count as expected
- [ ] Title page correct
- [ ] Character names format correctly
- [ ] Dialogue layout proper
- [ ] Transitions right-aligned
- [ ] No orphaned elements

## Version Naming

### Convention
```
[Title]_v[Major].[Minor]_[YYYYMMDD].[ext]
```

### Examples
```
Seoul_Identity_v1.0_20251227.pdf
Seoul_Identity_v1.1_20251228.pdf
Seoul_Identity_v2.0_20260115.pdf
Seoul_Identity_v2.0_20260115.fdx
```

### Major vs. Minor
- **Major (1.0 -> 2.0):** Significant rewrite
- **Minor (1.0 -> 1.1):** Polish, small changes

## Troubleshooting

### PDF Issues
| Problem | Solution |
|---------|----------|
| Wrong fonts | Check PDF config, ensure Courier |
| Bad margins | Verify config matches standards |
| Missing title page | Enable in config |
| Notes appearing | Disable print_notes |

### FDX Issues
| Problem | Solution |
|---------|----------|
| Elements misformatted | Review in Final Draft, adjust |
| Notes missing | Expected - FDX doesn't support all |
| Dual dialogue broken | May need manual fix in FD |

### HTML Issues
| Problem | Solution |
|---------|----------|
| Print looks wrong | Use paper size option |
| Styling off | Use default CSS or customize |

## Export Checklist

### PDF Delivery
- [ ] Page count within target
- [ ] Title page per standards
- [ ] No scene numbers (spec)
- [ ] No WGA numbers (spec)
- [ ] Filename follows convention
- [ ] File under 10MB

### FDX Delivery
- [ ] Opens in Final Draft
- [ ] Elements formatted correctly
- [ ] Scene headings intact
- [ ] Dialogue blocks correct

### Competition Submission
- [ ] Format matches guidelines
- [ ] Page count within limits
- [ ] Anonymous if required
- [ ] Filename as specified
Files in this package (2)
  • README.md 2 KB
  • SKILL.md 5 KB

Versions

RepositoryScoreLicence
This page · bybren-llc/story-systems-template100MIT
bybren-llc/story-systems-template100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 50a66e726c01 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100fountain-syntax
    This skill provides complete Fountain screenplay format syntax reference. Covers title page, scene headings, action, character names, dialogue, transitions, notes, sections, and all special formatting elements. Use when: writing or editing .fountain files, validating screenplay…
  • 95fountain-syntax
    Complete Fountain screenplay format syntax reference. Covers scene headings, action, character names, dialogue, parentheticals, transitions, dual dialogue, notes, title page, emphasis, and page breaks. Use when: writing or editing .fountain files, validating screenplay format,…
  • 86screenplay-studio
    Run Screenplay Studio, the story-to-narrated-video pipeline built on a Marvin workspace. Use for writing a Fountain screenplay from an idea so the import reads all of it, for cutting a Fountain screenplay into chapters, beats, characters, scenes and sounds in Marvin…
  • 100fountain-webhooks
    Receive and verify Fountain Hire webhooks. Use when setting up a Fountain (hourly-workforce hiring) webhook endpoint, verifying the X-OBIQ-SIGNATURE-V2 HMAC-SHA256 signature, debugging 401s, or handling applicant screening events (stage changes, background checks) and Post-Hire worker events.
  • 100adaptation
    This skill should be used when the user asks to "make an audiobook", "narration script", "narrator", "ACX", "Findaway", "pronunciation guide", "how long is the audiobook", "adapt to a screenplay", "Fountain", "screenplay", "picture book", "spreads", "illustration notes", "art…
  • 90sw-format-adaptation
    Screenplay format, page craft, the writing process and adaptation (剧本格式/写作流程/改编) — merged from Wendy Henson (spec format rules), Richard Walter (page craft, revision), Neill Hicks (selling vs shooting script, draft chain), Syd Field (master shot, card method, adaptation as…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.