Make the script easy to identify
A screenplay title page gives a reader the information needed to identify the script and its writer. The job is modest and precise: show a readable title, a clear writing credit and the appropriate identifying details. The generator above turns those entries into a one-page PDF or a Fountain title block. It does not rewrite the screenplay or require you to open a full screenwriting application just to create its first sheet.
Enter the script title and credited author name first. The writing-credit field begins with “Written by,” which you can change. Source credit, draft information and contact details are optional. Use the live preview to catch missing fields and obvious spelling problems, then download the result you need. A completed PDF opens as a separate title sheet that you can review before combining it with your screenplay elsewhere.
The PDF uses US Letter dimensions, 612 by 792 points, and 12-point Courier. The title and writing information sit in a centered block. Contact text goes near the lower left and a version or date can appear near the lower right. This is a straightforward layout for a reader who needs the document’s identity without decorative distractions.
The preview is approximate. Browser text rendering and the PDF’s fixed coordinates are different systems, so the downloaded PDF is the file to inspect before submission. Printing from the browser provides another layout route, while Fountain gives you text that a compatible screenplay application can interpret. Choose the output based on your next step rather than assuming the three formats are identical documents.
Decide which name belongs on the page
The author field holds the credit you enter. It can be a legal name, pen name or collaboration credit appropriate to the project. The tool does not verify authorship, assign writing credit or decide how collaborators should be listed. Confirm the wording with the people responsible for the script before exporting a document that will circulate outside your working group.
Keep the author entry on one line in the form. A collaboration can be entered as a single text credit, such as “Jordan Reed & Casey Lin.” That text is preserved; the generator does not reinterpret the relationship between the names. If a recipient requires a particular credit convention, follow that instruction and inspect the resulting layout.
Spelling deserves a separate check. A title page can look polished while carrying an outdated pen name or a missing collaborator. Read the author field aloud and compare it with the name used in your submission materials. The PDF metadata also uses the entered author name, so a last-minute visible change should be followed by a fresh download.
Some submissions ask for identifying information to be omitted. This generator requires an author name because its primary workflow is an identified screenplay title sheet. If your recipient requires a truly anonymous document, use the recipient’s specified process and check all file properties. Leaving a contact field blank does not by itself make a document anonymous.
Keep the writing-credit line simple
“Written by” is a practical default for an original script’s title sheet. The field is editable because real projects may need a different approved wording. Its purpose is to identify the relationship between the credited names and the screenplay. It is not a place for a paragraph explaining the project’s history or a promotional statement about the writer.
A short credit line works best with the centered layout. The form accepts up to eighty characters in that field and keeps it on a single logical line. The PDF may wrap long entries within its available width. If the result looks awkward, simplify the wording rather than shrinking the type to fit an increasingly complicated credit block.
Do not confuse the writing credit with the optional source credit. A screenplay adapted from another work can identify its screenwriter and separately describe the source. Keeping those concepts in different fields makes the page easier to read and avoids a title block that mixes several roles into one ambiguous sentence.
The generator provides formatting, not a decision about who receives credit. If that decision is unsettled, resolve it through the project’s normal collaboration process before distributing the page. A clean export cannot make an unresolved agreement clearer. The tool intentionally preserves your chosen text instead of generating a confident-looking credit from incomplete information.
Add a source line only when it helps the reader
The source field can hold wording such as “Based on the novel by Alex Morgan.” It is optional because an original screenplay does not need a source statement merely to fill space. When you do include one, make it specific enough to identify the underlying work or contributor in the manner your project requires.
A source statement and a script title serve separate purposes. The screenplay may have a different title from the book it adapts. Put the screenplay’s title in the main title field and the relevant source wording below the writing information. Do not force both titles into one long heading if that makes the document harder to identify.
The field accepts up to two hundred characters as one logical line. The PDF wraps it into readable lines as necessary. A long chain of development history, edition details and acknowledgments can overwhelm a first page. Move information that the reader does not need immediately into the accompanying materials or the appropriate part of the screenplay package.
This page does not determine adaptation permissions or certify the source credit. It helps you display a statement you have already chosen. If you are developing a film from your own book, the Book-to-Screen course provides a broader workflow for turning story material into a short film, including lessons that address project preparation and source considerations.
An illustrative original screenplay
The sample details describe a fictional project called THE LAST TRAIN, credited to Alex Morgan. They are invented to demonstrate the form and are not presented as a real production or submission. With only the title, “Written by,” author and example email entered, the page contains a compact identity block and a contact line.
Try the sample, then replace the title and author before exporting. A common mistake with any document generator is leaving a convincing sample name in an otherwise finished file. Review the preview from top to bottom rather than checking only the field you edited most recently. Optional fields can also carry sample content, especially an example email address.
Now add a version label such as “Rehearsal draft — October 2026.” The date field is plain text rather than an automatic current-date stamp, so it stays under your control. A fresh download on a later day does not silently turn an older script into a newer draft. The entered label should describe the actual version attached to the title sheet.
If you add a source statement, the centered block becomes longer. Inspect the exported page after that change. The purpose of the example is to show how a small number of fields create a usable result, while reminding you that every additional line affects the page. A title sheet should identify the script cleanly without requiring a reader to decode a crowded hierarchy.
A second example: an adaptation working draft
Imagine an invented short screenplay titled NORTH PLATFORM. Its screenwriter credit reads “Jordan Reed,” and the source line says “Based on the short story by Casey Lin.” A draft label identifies the workshop version. These hypothetical details demonstrate separate roles in a single document; they do not prescribe the correct wording for another project.
Enter NORTH PLATFORM as the title and Jordan Reed as the author. Keep the source statement in its dedicated field. Add only the contact information the intended recipient needs. If the page is going to an internal workshop, an email address may be enough. A production packet may use different information, but more detail should have a clear purpose.
Download Fountain and examine its metadata block. You should see labeled title, credit, author, source, draft-date and contact entries when those fields are present. The values are indented on following lines. That structure preserves multiline fields without accidentally turning a line of title text into a new metadata key.
Download PDF as well if the next person needs a fixed page. Open it and compare its title, author, source and version with the Fountain block. Both derive from the same form entries, but they serve different workflows. One is a rendered sheet; the other is source text for a compatible writing environment.
How the one-page PDF is constructed
PDF coordinates are fixed rather than responsive. One inch corresponds to seventy-two points, so a Letter sheet measures 8.5 by 11 inches. The generator places 12-point Courier text on a single page. It wraps long text within defined widths instead of reducing the type size until a crowded page becomes technically possible but unpleasant to read.
The title block begins around the upper-middle portion of the sheet, with the writing credit and author below it. An optional source statement follows after additional space. The contact and version areas sit toward the bottom. These positions are deliberate defaults, not measurements extracted from your screenplay’s body formatting or a recipient’s custom template.
Title text is limited to one hundred sixty characters and up to three entered lines. Author text allows one hundred twenty characters. Contact text allows four hundred characters across up to six entered lines. Other field limits keep the fixed page predictable. A character limit does not guarantee that every possible word arrangement will make a good title sheet, so the PDF also checks wrapping constraints.
Long uninterrupted strings cannot always be wrapped cleanly. An oversized web address or a single unusually long title word may need a shorter display form or a deliberate break. When the PDF cannot place such text under its rules, it reports a clear error instead of creating an unreadable page. Fountain remains useful when you need to preserve a longer source value for another editor.
Contact information should have a reason to be there
The contact field is optional. Use it for information the recipient is supposed to receive, such as an email address or an approved representative’s details. Do not include personal information simply because traditional examples show several contact lines. A title page often travels farther than the initial email attachment, so choose its content deliberately.
Line breaks let you separate a name, email and another short detail. Keep the block concise. The PDF wraps contact lines within a narrower area to leave room for the version text on the opposite side. If wrapping would require more than nine PDF lines, shorten the contact details or use Fountain to take the text into an editor with a different layout.
Check email spelling in the downloaded file, not only in your memory. A visually correct layout does not validate that an address exists or belongs to you. The generator treats contact details as text. It does not send a verification message, add a clickable submission workflow or contact anyone on your behalf.
If a recipient supplies a dedicated cover-sheet template, use that template. The value of this generator is speed and a clean common layout when such a template is unnecessary. It should not become a reason to ignore explicit instructions about identifying information, contact placement or required project references.
Fountain export is editable source text
Fountain represents screenplay information in plain text. Its title-page metadata can identify the title, author and related details before the script body. The Fountain syntax reference describes that broader format. This generator exports the title block, leaving the rest of the screenplay to your writing application or existing Fountain document.
Each exported field has a metadata label followed by indented value lines. Multiline titles and contact details retain their line structure in those values. An empty optional source, date or contact field is left out of the output. The writing-credit line falls back to “Written by” if you clear it, keeping the title block coherent.
The Fountain download uses UTF-8 text. Names and titles containing characters outside the PDF font’s repertoire remain intact. If you later open the file in another application, that application chooses how to render its text and title page. A successful text export does not guarantee that every editor uses the same typeface, paper size or line breaks.
When inserting the block into an existing Fountain script, avoid leaving two competing title-page sections. Compare the new metadata with the existing document and keep the intended version. This tool does not merge files or inspect your full screenplay. It gives you a precise block to copy or download so you can integrate it knowingly.
Unicode and PDF font limits
Unicode support in a text field is broader than support in a particular embedded or built-in PDF font. The form and Fountain output preserve the entered text. The PDF uses the standard Courier character set, which can represent many familiar Latin characters but cannot encode every writing system or emoji. That difference is handled as an export constraint, not a reason to silently change somebody’s name.
If PDF generation encounters an unsupported character, it stops and explains the available choices. Download Fountain to retain the original wording, or use supported characters if that is appropriate for your project. The generator does not replace unknown characters with question marks and label the resulting file a successful export.
An accented Latin name can work while a title in another script does not. The distinction depends on the font’s actual encoding rather than on whether the browser preview looks correct. This is another reason to inspect the PDF result separately. The browser may display a character through a fallback font that the fixed PDF does not use.
For a multilingual screenplay package, take the Fountain block into an application that supports the needed fonts and follow the recipient’s document requirements. This page makes a clean common title sheet within explicit limits. It does not claim to provide every font, language layout or submission template used across film industries.
Printing and downloading are separate actions
Download one-page PDF creates the rendered file immediately after validation. The button does not send you to another form to type the same details again. If a field or font constraint prevents creation, the page keeps your inputs and shows the error. Correct the issue and try the action again with the values still present.
Print title page opens the browser’s print flow using the same entered content in a dedicated printable layout. Browser printing can add headers, footers or scaling depending on your settings. Turn off unwanted browser decorations and inspect the preview before printing. For a fixed electronic attachment, prefer the downloaded PDF over a casual print-to-PDF setup you have not checked.
Copy Fountain sends the metadata block to the clipboard when clipboard permission is available. Some browser contexts restrict clipboard access. If copying fails, the form remains usable and the download option provides the same text as a file. The export action should never require you to reenter a title merely because one output route was unavailable.
Downloaded files use a generic filename so you can recognize their purpose. Rename the chosen file to match your project and draft convention before distributing it. The file’s visible title, metadata and filename should point to the same screenplay version. A carefully formatted first sheet is less useful when its attachment name refers to a different project.
Check the title sheet against the script
A title page is one part of a screenplay package. Confirm that the title matches the script body and accompanying materials. Check the credited names, draft label and source statement. If your screenplay editor already generated a title page, decide whether to replace that page rather than accidentally adding a second first sheet.
This tool does not merge the title PDF with another PDF or add page numbers to the screenplay body. Use your normal document workflow for that step, then open the combined result from the beginning. Verify that the title sheet appears once and that the first screenplay page follows it in the intended order.
The screenplay format checker helps inspect the writing structure, while the screenplay runtime calculator starts from formatted page counts and timing assumptions. When counting pages for runtime, distinguish the title sheet from story pages. A printed title does not automatically add a minute to the film.
For pre-production planning after the writing pass, the script breakdown generator organizes scene headings, cast and production requirements. That workflow begins with the screenplay content, whereas this page handles only its identifying sheet. Keeping those jobs separate gives each output a clear purpose instead of turning a simple title form into an entire production system.
A final reading before you send it
Read the PDF as though you had never seen the project. Can you identify the script immediately? Is the writing credit easy to understand? Are optional details useful rather than distracting? A title page does not need a slogan, a synopsis or a visual theme to perform those basic jobs well.
Compare the exported content with the form one last time. Check unusual punctuation, accents, long source statements and contact lines. Make sure no demonstration text remains. If you changed a field after downloading, create a fresh output rather than assuming the existing file updates itself. Each download represents the form at the moment you pressed the button.
The entered title and contact text are processed in this browser. Tool measurement records actions such as starting or exporting, without sending those field values as event metadata. The downloaded document itself necessarily contains the information you chose to include. Store and share that file according to your project’s normal practices.
When the title sheet is correct, return to the screenplay. A clean first page helps the reader begin, but the script’s scenes, dialogue and structure still carry the work. Use BookWriter’s screenplay workflow when you want to move beyond the title sheet into planning the actual story and film, or follow the free course when you prefer a guided first project.