Fountain Export For Screenplays, Paste That Works Like Paste Again, And Tables Screen Readers Can Finally Hear -- Plotiar Product Updates (August 2026)
A screenwriter wrote in a few weeks back asking something that sounded, on its face, like a small request: could she draft a scene in Plotiar and hand the file to a co-writer who works in Final Draft. Simple question, deceptively hard answer, because a screenplay format like Fountain has no tags for "this is a character name" or "this is action" -- a reader has to work it out from capitalization and spacing, the same way a human reader would. Getting that inference right in both directions turned out to be most of this stretch's work. Here's what shipped.
Your Screenplay Can Now Leave Plotiar As Fountain
Plotiar could already bring a Fountain-formatted screenplay in. It can now send one back out, so a screenwriter drafting in Plotiar can hand the result to a collaborator using Final Draft, Highland, Slugline, or Fade In, and have it open correctly. Export a document, choose Fountain alongside the existing Word, PDF, and EPUB options, and the file comes out formatted the way the format expects -- character cues in capitals with dialogue underneath, action lines as plain paragraphs, centred text staying centred. We tested it by round-tripping a real screenplay through export and back through import repeatedly until the text stopped changing at all, then read the output back with an independent Fountain parser -- not our own -- to make sure a collaborator's software would agree with ours about what every line means. Two things it caught along the way: a multi-line speech was coming back out as several separate paragraphs instead of one continuous block, and centred text like a title card was losing its centring. Both are fixed, so a "> THE END <" now survives the trip.
Paste Works Like Paste Again
A cluster of clipboard bugs got closed out together, because they all touched the same code path. Plain Ctrl+V had quietly stopped working for anyone who reached it by keyboard rather than through a menu -- a paste would seem to do nothing at all. It's fixed, and paste-without-formatting is fixed alongside it: choosing it now genuinely keeps your text exactly as it arrived, instead of still turning a leading dash into a bullet or "1." into a numbered list, and it's reachable from the paste menu itself rather than a keyboard shortcut nobody could discover. If you copy a table out of a markdown file, it now lands as an actual table instead of a wall of separate lines each holding a row of pipe characters. And a markdown link written in reference style -- the kind where the link text and its URL are defined on separate lines -- used to lose its destination entirely on paste, leaving behind just the link text with nothing to click. That construct is common enough in hand-written markdown that it was worth fixing on its own.
Tables Render At The Right Size, And Screen Readers Can Hear Them
Two rendering bugs in tables are fixed. Columns were being measured against a slightly smaller font than the one they're actually painted in, so every column came out a little too narrow and text could clip inside it. And a single long cell -- a sentence in a "Notes" column, say -- was claiming space in proportion to its full unwrapped length, squeezing every other column in the same table down to a sliver even when those columns only held short, single words. Columns now get at least enough room for their longest single word before any extra space is divided up, so a long note wraps onto multiple lines instead of starving its neighbors. Separately, and more fundamentally: tables were invisible to screen readers. The accessibility layer had no path for reading a table's structure at all, so a writer using assistive technology got nothing back from a table in their own manuscript -- not a partial read, nothing. Tables now announce their content, row by row and cell by cell.
Smaller Fixes Worth Mentioning
A chapter name in Plot Grid that ran long was still getting cut off mid-word even after an earlier attempt to fix it -- it now gets a wider column and enough room to wrap across several lines before anything is truncated, with the full title still available on hover. Switching between files no longer resets your editor view back to the default; whichever mode you had open for a document is the one you'll find when you return to it. On mobile, an editor you hadn't touched in a while was quietly repainting itself many times a second just to blink a cursor that wasn't even there, which is exactly the kind of thing that drains a battery and makes an idle tab feel like it's struggling -- that's stopped. Clicking in the empty space just past the end of a line that ends in a footnote reference no longer opens the footnote instead of letting you keep typing. Two touch controls in Lore's view switcher were sized under the usual touch-target minimum and are now easy to tap. And an editing bug in collaborative documents that could, in one specific sequence involving a paste and an undo, quietly drop a paragraph from the shared document is fixed -- narrow, but exactly the kind of thing that shouldn't happen to anyone's manuscript.
Try Plotiar at app.plotiar.com.