The Story of Draftill: Why I Built My Own Screenplay Workspace

I have never wanted to write a screenplay in a blank document.

A blank page can be useful, but a screenplay is not only a collection of sentences. It is structure, timing, scenes, characters, locations, revisions, visual references, production questions, and hundreds of small decisions that must remain connected. I wanted the freedom to write, but I also wanted the work to stay organized. I did not want to fight margins in Word, imitate screenplay formatting in a general-purpose document editor, or keep the actual story scattered across files, browser tabs, notebooks, and half-forgotten folders.

For years, I kept looking for one place that felt natural. I tried Word and Google Docs. I tried Celtx, Final Draft, and other screenwriting applications. Every tool had something useful, and every tool taught me something about the way I work. But none of them felt like my complete workspace. Some felt too rigid. Some felt heavy. Some placed the screenplay in one box and everything around the screenplay somewhere else. Some made me feel as if I was borrowing a workflow instead of owning one.

That frustration became Draftill.

I did not need another text editor

The first mistake would have been to build a prettier version of Word. I was not looking for another place to type. I was looking for a place where a screenplay could think like a screenplay.

When I am working on a story, I need to move quickly between a scene heading, action, dialogue, a character, and the larger outline. I need formatting to support the writing instead of becoming a task of its own. I need comments, goals, statistics, keyboard shortcuts, and export controls close enough to be useful without crowding the page. I need the interface to disappear when the scene begins to work.

Traditional tools often solved one part of that problem. The trouble was what happened before and after the page. Character notes lived elsewhere. Location references lived elsewhere. Visual planning lived on another board. Earlier versions were copied into folders with names like final, final-new, and final-real. The screenplay was organized, but the creative process surrounding it was not.

I wanted a system that respected both sides: the disciplined format of screenwriting and the messy, visual, unpredictable way an idea actually becomes a film.

The tool-hopping years

I understand why established screenwriting software works for many writers. Final Draft is familiar across the industry. Celtx introduced generations of creators to browser-based production tools. General document editors remain available almost everywhere. This is not a story about declaring those products useless. It is a story about admitting that they did not match the way I wanted to build.

I would begin in one application, take notes in another, collect images in a folder, create a rough flow in a design tool, and then return to the screenplay hoping the structure was still alive in my head. Every switch cost a little attention. Every disconnected tool created another version of the truth. Eventually, the workbench became more complicated than the work.

Reliability, to me, is not only whether an application opens or saves a file. A creative tool is reliable when I can trust the whole process around it. It should help me understand where the story is, what changed, what still needs to be solved, and how the written page connects to production. It should give me room to experiment without making me afraid of losing yesterday's draft.

And freedom is not simply a zero-rupee price tag. Freedom means being able to shape a workflow around the project. It means keeping important data close, choosing when online services are involved, and not feeling trapped inside a feature hierarchy that was designed for somebody else's priorities.

By 2026, the missing piece was impossible to ignore

By 2026, artificial intelligence had entered almost every serious conversation about creative software. Yet I still could not find the combination I wanted: proper screenplay writing, visual pre-production, local version checkpoints, connected story libraries, and contextual AI that could understand the active work instead of behaving like a separate chatbot.

I did not want an AI button added to a toolbar so a product could say it had AI. I wanted assistance that could understand the selected text, the current page, a chosen Freeflow node, or the relevant part of the project. More importantly, I wanted it to help inside the workspace. If I asked for a revision, an outline change, a new character direction, or a visual reference, the result should have a clear path back into the work.

That distinction mattered. A generic chat window can produce ideas. A real creative assistant should understand where those ideas belong.

So I stopped waiting for the perfect application to arrive. If something keeps getting in the way long enough, eventually I bring it into the cave, put it under the light, and build the tool I wish had been there.

Draftill began as a refusal

Draftill began with a simple refusal: I would not accept that organized screenwriting had to feel restrictive, or that creative freedom had to mean chaos.

The name itself carries that intention. A draft is never the whole story; it is the version brave enough to exist today. Draftill is meant to be the place where that version can be written, questioned, mapped, compared, and refined without losing the thread that made it worth writing in the first place.

I built the editor around screenplay elements, reusable structure, typography controls, outline navigation, comments, writing goals, statistics, and shortcuts. The point was not to display a long checklist of features. The point was to reduce friction. When the software handles structure quietly, the writer gets to spend more attention on rhythm, intention, and character.

Export matters too. A screenplay does not stay inside the application forever. It needs to become a readable, structured PDF that can travel to collaborators, actors, and production conversations. Draftill keeps that handoff close to the writing workflow instead of treating it as an afterthought.

Freeflow is where pre-production gets a wall of its own

Writing a screenplay is linear because the audience experiences time in sequence. Planning a film is rarely linear. A location may affect three scenes. A visual reference may unlock a character. A prop may connect an early setup to a later payoff. A production problem can force the story to find a better answer.

That is why I created Freeflow. It is not simply a diagram that shows how a story connects. It is a free-form pre-production visualization space: a canvas for scenes, shots, characters, notes, images, media, links, previews, and checklists. You can arrange ideas spatially, group them, connect them, and keep the full production thought visible.

For me, Freeflow is the digital version of the wall in a detective's workspace—the place where separate clues become a pattern. The difference is that every node can remain part of the same application as the screenplay. The board does not replace the script. It gives the script another way to reveal what it needs.

Characters and locations needed to stay close

A character is more than a name that appears above dialogue, and a location is more than a scene heading. Both collect visual references, history, practical constraints, relationships, and recurring details. When those notes are scattered, continuity becomes a memory test.

Draftill keeps character and location libraries inside the workspace so I can move from the page to the people and places behind it. Images and screenplay references remain close to the material they support. This sounds like a small convenience until a project grows. Then it becomes the difference between guessing and knowing.

Checkpoints make experimentation safer

Creative work needs the ability to take a dangerous turn. Sometimes the right choice is to remove a scene, reverse a motivation, or rewrite an ending. The fear is not only that the experiment might fail; it is that the version before it might disappear.

Draftill uses local screenplay checkpoints so a writer can preserve a meaningful version, compare changes, and roll back when another direction was stronger. I wanted version history to feel understandable, not like a technical system borrowed from software development. Save a moment. Explore. Compare. Return if necessary.

That small sense of safety creates more freedom than any motivational message. When I know the previous draft is still there, I can be ruthless with the current one.

AI should understand the workspace—and remain optional

Draftill AI is designed around context. It can work with the active workspace, selected screenplay text, and selected Freeflow nodes. Where a provider and model support them, external tools can also assist with web research or image generation. The goal is not to replace the writer. The goal is to remove the distance between a useful conversation and a useful change in the project.

I also wanted a real choice in how that assistance runs. Draftill supports provider-based models, while private local models can run through the bundled local runtime. Downloaded local model files stay on the computer, and provider API keys are stored locally with protected storage. AI is there when it helps. It can stay out of the way when it does not.

That boundary matters to me. A screenplay workspace should not demand that every creative thought pass through a remote service. The user should understand what is local, what requires an external provider, and what is being shared when they choose a particular capability.

Public source, deliberate boundaries

I made Draftill's source public because transparency matters. People should be able to inspect how the application works, reproduce an unmodified build, and understand what is running on their machine. At the same time, Draftill uses a custom source-available license with clear boundaries around modification, redistribution, resale, white-labeling, and hosted-service use.

That choice is intentional. Openness should not require pretending that authorship, maintenance, and product identity have no value. I want Draftill to be inspectable and trustworthy while protecting the years of thinking that shaped it.

What Draftill is today

Today, Draftill is a focused Windows desktop workspace for screenplay writing and visual pre-production. It brings together the screenplay-first editor, Freeflow canvas, characters, locations, local checkpoints, production-minded PDF export, comments, goals, statistics, keyboard shortcuts, and optional AI assistance.

More importantly, it is evidence that frustration can become architecture. Every feature began with a real interruption in my own process: a tab I did not want to reopen, a draft I did not want to lose, a reference I could not find, a tool that knew nothing about the scene in front of me, or a planning board separated from the words it was supposed to support.

Draftill is not built from the idea that technology can write a great film for us. It is built from the belief that better tools can protect the attention required to write one.

The story is still being written

I know Draftill will continue to change because my understanding of the problem continues to change. Every screenplay exposes another edge case. Every production thought asks for another kind of connection. Every useful AI interaction makes the useless ones easier to identify. That is not a weakness in the product. It is the nature of building a serious creative tool.

I am building it in the same way I write: one deliberate draft at a time. Some nights are spent polishing what is already visible. Other nights are spent deep in the machinery, making sure the quiet parts remain dependable. The work is not glamorous every day. It does not need to be. Gotham was not saved by a landing page.

Draftill exists because I wanted the discipline of screenplay format, the freedom of a creative wall, the safety of local versions, and the intelligence of modern tools in one place I could trust.

See Draftill, then follow the next chapter

You can explore the features, screenshots, source, license, and current Windows download on the Draftill project page. If you are a screenwriter, filmmaker, developer, or simply someone who cares about better creative tools, I would like to hear what you think.

Follow the build and the work around it on X, Instagram, LinkedIn, and GitHub. Draftill started as the tool I needed. The next chapter is making it useful for every writer who has felt the same gap.