Flying Pixels

Erroneous depth points at object edges in a depth map, floating between the foreground and background.

Flying pixels are a common artifact in depth data at object outlines: edge pixels that should belong to either the foreground or the background instead get a depth value somewhere in between, which, once converted to a point cloud, becomes a scatter of points floating in midair — like a veil trailing off the object’s edge. In ToF (time-of-flight) depth cameras, this happens because a single pixel receives light reflected back from both the foreground and background at once, measuring a mixed signal; Microsoft’s Azure Kinect documentation classifies this kind of edge pixel as a multipath problem and marks it invalid. In stereo matching and depth-estimation networks, regression output gets smoothed across sharp depth discontinuities, which also produces flying pixels. Flying pixels cause errors in grasp poses and collision checking, and a common fix is filtering out suspicious edge points based on depth gradient or neighborhood consistency.

ExamplePixel-Perfect Depth (NeurIPS 2025) points out that generative depth models which compress a depth map into a latent space with a VAE first introduce flying pixels at edges and fine detail, so it instead does diffusion generation directly in pixel space, producing a point cloud with almost no flying pixels.

Also called

Flying Points, Mixed Pixels

Related

Depth Camera · Time of Flight · Depth Map · Point Cloud · Depth Holes · Monocular Depth Estimation

Sources

Azure Kinect DK depth camera（Invalidation / Multi-path 一节） (Chinese)
Pixel-Perfect Depth with Semantics-Prompted Diffusion Transformers