gradio-app/gradio

Choose this fork if you want a faster, customized Gradio experience and can tolerate drift from upstream. Choose upstream if you need the latest fixes, compatibility work, and lower merge risk.

Prefer upstream Gradio unless you specifically need this fork’s older, simplified, or customized behavior. This fork is useful for niche productized use cases, but it is stale and materially diverged, so it is a poor choice for most adopters who want active maintenance and feature parity.

Prefer upstream unless you need this fork's older behavior or its specific UI/docs additions. For most adopters, the stale activity and large divergence are a strong signal to avoid it as a base for new work.

Choose this fork only if you specifically need its customized website/docs workflow and are willing to absorb upstream drift. For most adopters who want current Gradio behavior, upstream is the safer choice.

Choose this fork only if you need its specific downstream customizations and are prepared to own rebase and maintenance work. If you want a broadly supported Gradio base with the latest fixes, upstream is the safer choice.

Choose this fork only if the localization or downstream-specific workflow is the goal. If you want current Gradio features, fixes, and active maintenance, upstream is the better default.

Choose this fork only if you want a materially customized Gradio and can tolerate rebase overhead. For most adopters who want stability and upstream parity, the main Gradio repo is the safer choice.

Prefer this fork only if its custom path controls or component-specific changes are required. For most adopters, upstream Gradio is the better choice because this fork is stale, materially behind, and likely missing important maintenance and compatibility fixes.

Choose this fork only if its custom changes are specifically what you need and you are prepared to own a large maintenance gap; otherwise upstream is the safer choice for current compatibility and bug fixes.