How it works

Two products that behave like one: PP Studio, where you make the image, and PP Library, where its photographs come from.

1. 01

   Build the image as a graph

   Instead of stacking layers and baking every edit into the pixels, you connect nodes: import a photo, correct its colour, paint over it, blur it, blend it with another. Each node is one step, and the graph is the whole recipe of the image.

2. 02

   Change your mind at any step

   Edit a node from an hour ago and everything after it updates. Try three skies, keep two variants, go back to the first — the client's next request is an edit, not a repaint.

3. 03

   Work at full resolution, in film colour

   The whole graph is computed on the GPU in 16-bit floating point and linear light, with ACES colour management, so very large images stay responsive and keep their quality through heavy processing.

4. 04

   Find a photo without leaving the app

   Press F2 and PP Library opens in its own window inside PP Studio. Search, download — and the app catches the download as it happens: the original is written into your project and arrives as a node. No downloads folder, no re-import.

5. 05

   Connect it to the rest of your chain

   Images go in and out in standard formats — EXR, TIFF, PNG, JPEG — and an embedded Python environment lets a studio script PP Studio and plug it into its pipeline.

6. 06

   Nothing leaves your machine

   The project, the paint, the graph — all local. The cloud holds the library and nothing else.

One account signs you into both. Signing out of the library does not sign you out of PP Studio — they share an identity, not a session.