Does Pockitle Cue replace QLab?

No. QLab remains a show-control environment for sound, video, lighting, and cue playback. Pockitle Cue focuses on subtitle-specific preparation, cueing, projection, and audience mobile delivery.

When can QLab be enough for surtitles?

It may be enough when surtitles are only a projected cue layer inside an existing QLab show file and the production does not need script review, language selection, or audience phone delivery.

QLab for Surtitles | Pockitle Cue

Short answer

Keep QLab for the show timeline and use Pockitle Cue for script preparation, translation review, and audience-phone delivery. Export reviewed text as local QLab Text cues, or rehearse the selected Cloud Sync beta when phones should follow QLab GO. QLab alone can fit a stable projection-only cue list.

QLab is publicly positioned as macOS software for sound, video, light, and show-control cues. That makes it a familiar technical environment for many theatre teams. Pockitle Cue does not need to replace that environment: QLab can keep running the local show timeline while Pockitle Cue prepares subtitles and, when needed, keeps audience phones in sync.

Review scope: the official QLab 5 manual and Text Cue documentation, reviewed on 2 October 2026. Pockitle Cue is not affiliated with QLab or Figure 53. This page compares when QLab alone is enough, when Pockitle Cue should own the subtitle workflow, and when the systems should work together.

Workflow Comparison

Decision area	QLab alone may fit when...	Pockitle Cue with QLab may fit when...
Core use	The venue needs one cue timeline for sound, video, lighting, and local projection.	The show still runs in QLab, but subtitles also need preparation, review, deployment, or audience-phone delivery.
Subtitle preparation	Surtitles are already prepared and can be treated as part of a broader cue or media workflow.	The workflow starts from script intake, AI-assisted structuring, translation, review, and cue simulation.
Output model	The show only needs in-venue projection from QLab Text cues.	The show needs projection plus QR-code audience-phone subtitles from the same subtitle source.
QLab integration	The team is comfortable building and maintaining subtitle Text cues directly in the QLab show file.	The team wants to export reviewed Pockitle Cue subtitles into QLab, then optionally sync QLab cue jumps through Pockitle Cue.
Show-time recovery	Recovery only needs to happen inside the local QLab workspace.	Cue corrections should keep local projection and audience phones aligned without issuing new viewer links.

Where QLab May Fit Better

The venue already uses QLab as the show-control center for sound, video, lighting, or projection cues.
Surtitles are only one projected cue layer inside a larger technical design.
The technical operator is already trained in QLab and does not need audience mobile delivery.
The production wants a single backstage cue environment rather than a subtitle-specific workspace.
Pockitle Cue may be more than the team needs if surtitles are only a simple projected cue layer inside an existing QLab show file.

Where QLab and Pockitle Cue May Fit Together

The team wants QLab to remain the venue timeline for sound, lighting, video, standby cues, and local projection.
The subtitle team wants Pockitle Cue for script preparation, translation review, cue checks, and stable subtitle identities.
Before deployment, Pockitle Cue can export a QLab Projection Pack for local QLab Text cues without audience links or cloud sync.
After deployment, the selected QLab Cloud Sync beta can mirror QLab subtitle cue jumps through Pockitle Cue to audience phones; rehearse that connected path separately from local Text cues.
Existing QLab sound, lighting, video, and standby cues can remain around the subtitle groups in the show file.

Where Pockitle Cue May Fit Better

The subtitle workflow starts with a script, translation, and review rather than a finished cue list.
The production needs language selection and subtitles on audience phones.
The operator needs subtitle-specific recovery, cue jumps, blackout, and projection/mobile coordination.
Non-QLab users such as production managers, translators, or access coordinators need a browser workspace.

Questions to Ask Before Choosing

Are surtitles only one cue layer inside a larger show-control file, or are they a workflow that needs review and handoff?
Will translators, production managers, or access coordinators need to work outside the show-control workspace?
Does the production need only local projection, or should audience phones follow the same subtitle cue state?
Should QLab remain the operator timeline while Pockitle Cue handles audience delivery and subtitle state?
What recovery path should the team use if the live performance moves off the expected cue sequence?

Further Planning Reading

For the QLab product overview, continue with QLab-compatible surtitles with Pockitle Cue. For export-only setup, continue with Export QLab Projection Pack. For deployed-show sync, continue with QLab + Pockitle Cue Sync beta.

QLab for Surtitles: Show Control, Projection Pack, or Cloud Sync?