• Home
  • Blog
  • Gallery
  • Pricing
  • Home
  • Blog
  • Gallery
  • Pricing
Start creating

Create.Play.

Creator blog

Home/Blog/Product workflow

Landscape or Portrait, PC or Web: Decide the Release Format Before Writing the Script

The release format is not a packaging option to choose after the script is finished. Landscape or portrait determines actor positioning and subtitle space; PC or Web determines input methods, video storage, loading strategies, and distribution paths. The team should decide on a primary aspect ratio and platform before building the three-minute prototype at the latest.

D
DramaFork Editorial TeamInteractive storytelling and AI production
2026.08.18Estimated reading time: 12 min
Blog cover for “Landscape or Portrait, PC or Web: Decide the Release Format Before Writing the Script”
Article contents
Creator blog
  1. 01Introduction
  2. 02Landscape and portrait change more than composition
  3. 03PC, Web, and mobile each have major constraints
  4. 04Choose based on player tasks, not team preferences
  5. 05The platform determines the video integration approach
  6. 06Create a release format decision table
  7. 07State three things clearly in the project initiation document
  8. 08Check the release format before starting work
Back to article top

Introduction

The release format is not a packaging option to choose after the script is finished. Landscape or portrait determines actor positioning and subtitle space; PC or Web determines input methods, video storage, loading strategies, and distribution paths. The team should decide on a primary aspect ratio and platform before building the three-minute prototype at the latest.

This article provides a framework for decisions at project initiation; it does not mean every project must release on only one platform. Choosing a primary platform first gives the initial version technical and viewing conditions that can be validated; porting should take place after the core experience is stable.

Landscape and portrait change more than composition

Landscape is better suited to multiple people in the same frame, environmental clues, surveillance footage, and traditional PC/console viewing. Players can look across a wider area, and subtitles and choices are easier to place below or beside the image.

Portrait is closer to one-handed viewing on a phone. Characters’ faces and interpersonal conflicts can more easily occupy the center of the frame, but there is less space for environmental information. Subtitles, options, countdowns, and system prompts compete for the same area. If safe areas are not reserved during filming, post-production can only cover up performances or reduce the text size.

Do not assume you will shoot both a landscape set and a portrait set. Cropping landscape footage to portrait loses character relationships and clues, while placing portrait footage in landscape leaves large amounts of empty space. Supporting both aspect ratios means recomposing shots, checking subtitles, exporting assets, and testing interfaces, and should be budgeted as a separate cost.

PC, Web, and mobile each have major constraints

A PC client suits larger video packages, keyboard and mouse or controller input, offline saves, and Steam distribution. Its costs include installation, builds, platform reviews, and more variation between devices.

A Web version has a low barrier to entry and makes prototypes easy to share, but browser autoplay rules, network fluctuations, caching, decoding capabilities, and tab switching all affect the video experience. You cannot assume that the fast network on a development machine represents real-world conditions.

Mobile suits portrait orientation and short sessions, but requires handling touch target areas, system interruptions, resuming from the background, storage space, different screen aspect ratios, and store rules. Users are also more likely to watch with the sound off, so subtitles and non-audio feedback should be designed from the first version.

Choose based on player tasks, not team preferences

If the core task is comparing several surveillance feeds and looking for details, landscape on PC is usually more natural. If the core task is quickly expressing a stance during a short drama’s conflict, portrait on mobile is closer to actual usage conditions. If the core goal is to let prospective users experience a three-minute prototype without installing anything, Web can serve as the validation platform.

The full version of 《零点回拨》 includes a customer service interface, call records, surveillance footage, and evidence comparisons, making it suitable for landscape on PC; however, the three-minute version used for user acquisition can be built for Web, retaining one incoming-call judgment and one clear consequence. These are not simply two exports of the same project, but a complete product and a slice for validation.

The platform determines the video integration approach

Being able to “play” video is only the minimum requirement. Interactive film games also need to prepare the next clip in advance, switch quickly after a choice, handle pausing and resuming, and keep audio and video stable on low-spec devices.

Unity’s VideoPlayer.Prepare prepares resources before playback; Unreal Engine’s Media Framework supports local files, streaming media, audio and video tracks, and integration with Blueprint and UMG; Godot’s VideoStreamPlayer also has its own format and Web performance limitations. Check the target platform and encoding before choosing an engine, rather than discovering after filming that all the footage needs conversion.

Create a release format decision table

Rate each candidate option from one to five:

Dimension Facts to check
Player fit Whether target users actually use that device in that setting
Interaction fit Whether input, text, clues, and time pressure feel natural
Audiovisual fit Whether the aspect ratio can accommodate characters, subtitles, and options
Technical risk Whether video, caching, saves, and device differences are manageable
Distribution cost Accounts, reviews, assets, and the amount of version maintenance
User acquisition path Where players discover and enter the work
Team capability Whether the team has the relevant test devices and development experience

The scores do not automatically provide an answer. Any option scoring below three on “player fit” or “technical risk” should first undergo targeted prototyping, rather than having those weaknesses averaged out in the total score.

State three things clearly in the project initiation document

First: what the primary aspect ratio and platform are for the initial version. Second: why they best suit the target players and core task. Third: which platforms are not supported for now, and under what conditions they will be reconsidered.

Once the release format is decided, the script can account for how long a segment can last, how much information players can see at once, and how choices should appear. The next stage is to turn these constraints into the core loop.

Check the release format before starting work

When putting the plan into practice, record the target devices, aspect ratio, session length, input methods, and network conditions on the same specification card. Then test both landscape and portrait with a minimal segment containing dialogue, choices, subtitles, and video transitions. Proceed to the full script stage only after the team confirms that composition, interaction target areas, and asset costs are all viable.

Explore product capabilities Play interactive stories

Updated 2026.10.04

Explore this topicMaking interactive filmsCharacter and worldbuilding
PLAY / DISCOVER

Related works and experiences

Browse the works index
Interactive film · Concept preview

One Bed Left

One intensive-care bed remains and several patients need it. Every clinical decision carries a human cost.

Interactive film · Concept preview

The Black Rose Witness

Caught between a mafia marriage and a deadly testimony, a witness must decide whom to trust before the truth turns violent.

Interactive film · Concept preview

Elevator Thirteen

An elevator keeps stopping on a thirteenth floor that should not exist, where a missing reflection may know how to escape the loop.

Interactive film · Concept preview

Last Train to Tomorrow

The last train runs toward two futures: a thriving city and a ruined world. Your choices decide its final stop.

Continue reading

Browse more articles
Blog cover for “Before Writing the Plot, Define Who Will Play Your Work and in What Context”
Product workflow2026.08.17 · 13 min

Before Writing the Plot, Define Who Will Play Your Work and in What Context

The first document when starting an interactive film game should be a “target player context card,” rather than a character biography: who enters the experience, on what device, at what time, with what expectations, and why they stop. Only when that context is clear can the team decide segment length, choice countdowns, subtitle size, save points, and content promises.

Blog cover for “Keeping Choice Buttons, Subtitles, and Countdowns Clear of the Action: Landscape and Portrait Interaction…
Production practice2026.08.30 · 13 min

Keeping Choice Buttons, Subtitles, and Countdowns Clear of the Action: Landscape and Portrait Interaction Guidelines

The interface of an interactive film game is part of the shot composition, not merely a layer over the video. Choices, subtitles, countdowns, and system messages must share safe areas and priorities, with separate validation for landscape, portrait, distant TV viewing, and mobile touch input. The goal is to let players follow the story and operate the controls without competing demands on their attention, rather than to make the UI as invisible as possible.

Blog article cover for “From a One-Sentence Idea to a Player Promise: First Decide What Players Do in the Story”
Product workflow2026.08.17 · 13 min

From a One-Sentence Idea to a Player Promise: First Decide What Players Do in the Story

A one-sentence idea sparks interest; a player promise tells people “what I can do, and why my actions matter.” An interactive film game needs both from the outset. “A late-night customer service agent receives a call from twenty-four hours in the future” is only a story hook; “assess whether the calls are genuine, choose allies, and change what happens after midnight” is a player promise that can be verified.

From a story to a playable world.

Create interactive narrative games with DramaFork: connect scripts, characters, shots, and choices into a playable first version.

Explore & play

  • Explore gallery
  • Interactive film
  • Text game
  • Character IP
  • Rankings
  • Works index

Create & collaborate

  • My creations
  • Film studio
  • Text-game studio
  • Character studio
  • Creator partnership

Reading room

  • Creator blog
  • Story topics
  • Article archive

Story guides

  • Interactive storytelling
  • Making interactive films
  • Designing text games
  • Character and worldbuilding

Plans & credits

  • Pricing
  • Credits

Policies & support

  • Privacy
  • Terms
  • Cookies
© 2026 DramaFork/DramaFork · Interactive narrative games
Press Enter to send, or drag away and release.