Harold Halibut Guide English

How Harold Halibut was made

Quick answer

Every set, puppet and prop in Harold Halibut was built as a physical object and scanned into Unity, a process that started in 2012 and took about ten years. Nothing in the game is a digital-only asset.

Harold Halibut was built twice. First as sets, puppets and props assembled by hand in a studio in Cologne, from clay, wood, textiles and welded metal. Then again in Unity, where the physical pieces were scanned and animated into a game that shipped on 16 April 2024. Slow Bros. began the project in 2012 and describes the early years as part-time and unfunded, which puts roughly ten years between the first conversation and release.

Ten years, part-time and unfunded

The project started in 2012 as a dinner conversation about stop-motion and story games. That origin is less trivia than method: the people involved came at a game from the direction of built objects and filmed movement, not from the direction of software.

Money shaped the schedule. Part-time and unfunded at the start, Harold Halibut grew in the hours the people making it could spare, and the decade reads as a long accumulation of physical work rather than a conventional development cycle. Ten years is unusual for an indie adventure. For a production where every room, chair and fish has to exist before it can be photographed, it is closer to the expected cost.

Clay, wood, textiles, welded metal

Official Harold Halibut screenshot: a workshop set on the Fedora

Four materials carry the look: clay for faces and small forms, wood for structure and furniture, textiles for clothing and soft furnishing, welded metal for the ship itself. A corridor on the Fedora is not a texture painted onto a box. It is a set with a workshop in it, and the objects on the bench were made by a person before Harold ever stood beside them.

Which is why the screenshots read the way they do. Stop-motion has visible grain, a slight imperfection in every surface, and light that behaves the way it does on a table. Nothing in that look was simulated. It was built, and the scan carried it into the engine.

From the table to Unity

The pipeline is short to describe and long to do.

  1. Build the piece. A set, a puppet or a prop is made by hand at a size a person can work with, using clay, wood, textiles or welded metal depending on what it has to do.
  2. Scan the finished object. The physical piece is captured so its shape and its surface enter the project as data.
  3. Animate inside Unity. The scanned assets are assembled into scenes and moved in the engine, which is where Harold walks, doors open and the camera follows.

Everything after step three is ordinary game work: dialogue, localisation, platform builds. Everything before it is modelmaking, and modelmaking does not compress. The public account of the production does not name the scanning hardware or give frame counts, and no numbers are supplied here.

Who built what

Three people carry the credits that explain the look, and each of them sits on the physical side of the pipeline as much as the digital one.

CreditName or tool
Creator, director, design, composer, writerOnat Hekimoglu
Art director, puppetmakerOle Tillmann
Set architect, miniature carpenter, cinematographyFabian Preuschoff
StudioSlow Bros., Cologne, Germany
EngineUnity

Hekimoglu holds an unusually wide set of roles: story, design, music and writing all sit with the person who started the project at dinner. Tillmann's credit names the puppets directly, which is rare in a game and precise about where the craft labour went. Preuschoff's covers the architecture of the sets, the carpentry that made them and the cinematography that framed them.

The cast performs in English throughout, and the game ships with 11 store languages. Nothing in the credits points to a separate animation house, so the pipeline described above is the studio's own work.

Release and patch timeline

DateRelease or patchWhat changed
2012Project beginsDinner conversation about stop-motion and story games; part-time and unfunded
16 April 2024Launch, version 1.0First release on PS5, Windows and Xbox Series X/S
13 May 2024Patch 1 (1.0.5)No notes in the source record
23 May 2024Patch 2 (1.0.6)No notes in the source record
15 October 20241.1.1Italian language added
16 September 2025Mac versionReleased on Steam for macOS
12 November 2026Switch 2Switch 2 version released

Two patches within six weeks of launch, then nothing documented until a translation arrived in October. The notes for 1.0.5 and 1.0.6 are not in the record used here, so the version numbers are the whole story of that ten-day window: two quick builds, small enough that the studio treated them as housekeeping rather than news.

Cost of building a world by hand

The dates after launch are the honest measure of a physical pipeline. An Italian translation arrived about six months after release. The Mac build took until September 2025. Switch 2 landed two and a half years after the original. None of that is a complaint about the studio. It is what happens when new content means new objects on a table and a person at the table making them.

The trade-off runs both ways. The look is the reason the game exists, and the same decision is the reason new material arrives slowly. A shader can be edited overnight; a clay face cannot. Every extra line of dialogue that needs a new room behind it is a build, a scan and an assembly, and that is before anyone animates the result.

That also explains the shape of the release history. What the studio has shipped since 2024 is languages, a Mac build and one console port, not content. Players who finish the six chapters and the epilogue have seen the whole set.

If the production history is what brought you here, the platform page shows which of those builds exists on each machine, and the review breakdown is the other half of the story: what people made of the result in 2024 against how the last month of players scored it. For the cast of the ship itself, characters covers who everyone is, and the walkthrough picks up at chapter 1.