Horizontal and vertical Pokémon streams with OBS

The full path

1. NuzPoke: a main layout for horizontal and a secondary one for vertical, each with its own view URL.
2. OBS, horizontal canvas: your usual 16:9 scenes, with a Browser Source using the main layout's URL.
3. OBS, vertical canvas: a second 9:16 canvas, usually through a plugin, with its own scenes and a source using the secondary layout's URL.
4. Outputs: the platform and the broadcasting tool decide how both formats are sent.

Prepare the main and secondary layouts

1. Design the horizontal version in Stream → Main layout, for example a 6×1 strip.
2. Press + to create the Secondary layout: it copies every saved setting from the main one.
3. In the secondary layout, adapt distribution, alignment, spacing, name and background to the vertical frame. 3×2 or 2×3 usually fits better than a strip.
4. Copy the URL from each tab. The secondary one includes layout=2.

The team and its order are shared: you manage them once. All other visual settings are saved separately. The layouts guide covers each control.

Horizontal scenes

Create a Browser Source with the main layout's URL and reuse it in every horizontal scene (Add → Existing). OBS then keeps one page for that format and the team does not reload when you switch scenes. Starting values are in the OBS guide.

Vertical canvas and scenes

OBS works with one main canvas. For a second, vertical canvas, the option documented by Twitch is the Aitum Vertical plugin, which adds vertical scene and source docks:

1. Install the plugin and enable its vertical scene and source docks.
2. Create two or three vertical scenes; you can add existing sources and readjust them.
3. Add a Browser Source with the secondary layout's URL, 1080 wide and as tall as the area you reserve.
4. Link each vertical scene to its horizontal one so they switch together.

The gallery includes two vertical compositions with measurements.

Broadcast outputs by platform

These procedures belong to each platform and may change; review their official pages before an important stream.

Mobile readability checks

Twitch overlays its chat and controls on the vertical view and recommends keeping key visuals in the centre. Other platforms' apps do something similar. Before going live:

1. Run a test and watch it on your phone, both upright and rotated.
2. Check that nicknames read without zooming and types are not confused.
3. Make sure the team is not under the chat or the buttons.
4. Review the horizontal version on a rotated phone: that is what viewers see when they turn it.

The mobile reading examples and the contrast guide help fix whatever fails.

Two Browser Sources, two instances

Sharing a team does not turn the two sources into one: OBS runs one page per format, and Twitch warns that streaming two formats takes more resources. Measure with both outputs active using the performance rehearsal and, if needed, simplify the vertical composition by turning off Animate sprites in the secondary layout only.

Before you start streaming

1. The horizontal source uses the main URL and the vertical one the secondary URL.
2. No source uses the admin URL.
3. A test team change appears in both formats.
4. Vertical scenes are linked to horizontal ones.
5. The output is set up following your platform's help.
6. You have checked the vertical view on a phone.

Tools and documentation consulted

The main and secondary layouts were checked in a local NuzPoke environment. The OBS and platform flow is based on Twitch's Dual Format help, Twitch's June 17, 2026 announcement, YouTube's live streaming help and the OBS Studio 33.0 release notes, consulted on November 1, 2026. No live broadcast was made for this article and no resource usage was measured.