Hello,
I want to clarify NVIDIA’s official position on NvFBC / Capture SDK usage for Windows screen recording on consumer GeForce GPUs.
From the public Capture SDK license and documentation, it appears that NvFBC / Capture SDK usage is restricted to GRID, Tesla, or Quadro hardware, and not generally permitted on GeForce GPUs.
However, some consumer-facing software appears to expose NvFBC-related capture options on GeForce systems. For example, Steam Remote Play includes a setting named “Use NVFBC capture on NVIDIA GPU.” This creates confusion for independent developers, because it is unclear whether such access is available through an official NVIDIA partner/license path, legacy whitelist, private agreement, or some other permitted mechanism.
Could NVIDIA clarify the following:
-
Is there any officially supported or licensed way for an independent Windows application to use NvFBC / Capture SDK on GeForce RTX GPUs?
-
If some applications are allowed to use NvFBC on GeForce, what is the official process for requesting the same access?
-
If the public Capture SDK license restricts usage to GRID, Tesla, or Quadro hardware, does that mean GeForce usage is not permitted even if it technically works?
-
Is it permitted for software to ask the user for explicit consent and then patch, modify, or install a third-party patch for NVIDIA drivers to enable NvFBC on GeForce hardware?
-
From a technical perspective, NvFBC appears to be NVIDIA’s lowest-overhead capture path for feeding captured frames into a GPU/NVENC-based pipeline. If this path is restricted from independent GeForce software while selected consumer applications can expose it, how should independent developers obtain equivalent access, or is this access intentionally unavailable to them?
I am not asking for instructions to bypass restrictions. I only want to understand what is legally permitted, officially supported, and driver-stable, especially because other consumer software appears to expose this functionality.