Same weights. Same input images. Same seeds. Two inference paths that each reproduced their own results.

Yet 11.3% of the output's 8-bit channel values differed between them.

That was one result from verifying my unofficial PixRestore integration for ComfyUI . The difference was small—at most 5/255—but enough to make “matches the official output” an incomplete claim.

The useful part of this integration was defining exactly what “matches” meant: which execution mode, which process settings, and which representation of an image.

Here are the problems documented in the implementation and verification runs, and the checks that made the comparison meaningful.

First, define which official run you mean

PixRestore is an image restoration research project. Its released PixRestore-S model restores 512×512 images with one denoiser call, using DINOv2 features as conditioning. My integration exposes it through ComfyUI's usual image inputs and outputs.

The reference environment already required a decision.…