Go to file
Yuichiro Tachibana (Tsuchiya) b450cef156
Fix type the docstring of the Code component (#5905)
* Fix type the docstring of the Code component

* add changeset

---------

Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com>
2023-10-15 18:11:14 -07:00
.changeset Fix type the docstring of the Code component (#5905) 2023-10-15 18:11:14 -07:00
.config refactor: Use package.json for version management (#5514) 2023-09-15 16:23:52 -07:00
.devcontainer ensure login form has correct styles (#5324) 2023-08-24 16:42:28 +01:00
.github Always deploy to spaces (#5777) 2023-10-03 14:52:14 -04:00
.vscode Faster reload mode (#5267) 2023-08-29 17:29:15 -04:00
client Assert refactor in external.py (#5811) 2023-10-06 18:14:14 -07:00
demo Add styling (e.g. font colors and background colors) support to gr.DataFrame through the pd.Styler object (#5877) 2023-10-12 15:45:55 -07:00
gradio Fix type the docstring of the Code component (#5905) 2023-10-15 18:11:14 -07:00
guides add query parameters to the gr.Request object through the query_params attribute (#5681) 2023-09-25 22:25:09 -07:00
js Lite: Fix is_self_host() to detect 127.0.0.1 as localhost as well (#5886) 2023-10-13 13:57:21 +09:00
readme_files Refactor component directories (#5074) 2023-08-03 23:01:18 +01:00
scripts Removing .update and get_config, attempt 2 (#5240) 2023-09-18 21:17:06 -07:00
test Remove deprecation warning from gr.update and clean up associated code (#5890) 2023-10-15 17:58:06 -07:00
.dockerignore
.editorconfig Fix the wildcard in .editorconfig to match files in nested directories (#4165) 2023-05-11 10:29:28 -04:00
.git-blame-ignore-revs Add .git-blame-ignore-revs (#4586) 2023-06-21 15:08:27 -05:00
.gitignore Converting the website into sveltekit (#3437) 2023-07-04 16:33:22 +03:00
build_pypi.sh bash script (#5595) 2023-09-18 21:06:09 -07:00
CHANGELOG.md chore: update versions (#5817) 2023-10-05 19:55:12 -07:00
CITATION.cff
CONTRIBUTING.md docs: fix website directory in CONTRIBUTING.md (#5810) 2023-10-05 12:58:56 -07:00
globals.d.ts generate docs json in ci, reimplement main vs release (#5092) 2023-08-11 15:54:56 +01:00
LICENSE
package.json Validate i18n file names with ISO-639x (#5505) 2023-09-12 17:39:15 +01:00
pnpm-lock.yaml Keep Markdown rendered lists within dataframe cells (#5878) 2023-10-11 20:52:56 -07:00
pnpm-workspace.yaml unified release process (#4986) 2023-07-21 19:13:21 +01:00
pyproject.toml refactor: Use package.json for version management (#5514) 2023-09-15 16:23:52 -07:00
readme_template.md Refactor component directories (#5074) 2023-08-03 23:01:18 +01:00
README.md Update links to no longer give error 404 (#5482) 2023-09-18 21:38:53 -07:00
render_readme.py
renovate.json ignore svelte (#4656) 2023-06-23 12:58:28 +01:00
requirements-oauth.txt Sign in with Hugging Face (OAuth support) (#4943) 2023-08-10 15:12:40 -04:00
requirements.txt chore: update versions (#5796) 2023-10-05 14:10:45 -07:00
SECURITY.md
style.md Refactor component directories (#5074) 2023-08-03 23:01:18 +01:00
test-strategy.md Share button (#4651) 2023-07-05 19:50:17 -05:00
tsconfig.json generate docs json in ci, reimplement main vs release (#5092) 2023-08-11 15:54:56 +01:00

gradio
Build & share delightful machine learning apps easily

gradio-backend gradio-ui
PyPI PyPI downloads Python version Twitter follow

Website | Documentation | Guides | Getting Started | Examples | 中文

Gradio: Build Machine Learning Web Apps — in Python

Gradio is an open-source Python library that is used to build machine learning and data science demos and web applications.

With Gradio, you can quickly create a beautiful user interface around your machine learning models or data science workflow and let people "try it out" by dragging-and-dropping in their own images, pasting text, recording their own voice, and interacting with your demo, all through the browser.

Interface montage

Gradio is useful for:

  • Demoing your machine learning models for clients/collaborators/users/students.

  • Deploying your models quickly with automatic shareable links and getting feedback on model performance.

  • Debugging your model interactively during development using built-in manipulation and interpretation tools.

Quickstart

Prerequisite: Gradio requires Python 3.8 or higher, that's all!

What Does Gradio Do?

One of the best ways to share your machine learning model, API, or data science workflow with others is to create an interactive app that allows your users or colleagues to try out the demo in their browsers.

Gradio allows you to build demos and share them, all in Python. And usually in just a few lines of code! So let's get started.

Hello, World

To get Gradio running with a simple "Hello, World" example, follow these three steps:

1. Install Gradio using pip:

pip install gradio

2. Run the code below as a Python script or in a Jupyter Notebook (or Google Colab):

import gradio as gr

def greet(name):
    return "Hello " + name + "!"

demo = gr.Interface(fn=greet, inputs="text", outputs="text")
    
demo.launch()

We shorten the imported name to gr for better readability of code using Gradio. This is a widely adopted convention that you should follow so that anyone working with your code can easily understand it.

3. The demo below will appear automatically within the Jupyter Notebook, or pop in a browser on http://localhost:7860 if running from a script:

hello_world demo

When developing locally, if you want to run the code as a Python script, you can use the Gradio CLI to launch the application in reload mode, which will provide seamless and fast development. Learn more about reloading in the Auto-Reloading Guide.

gradio app.py

Note: you can also do python app.py, but it won't provide the automatic reload mechanism.

The Interface Class

You'll notice that in order to make the demo, we created a gr.Interface. This Interface class can wrap any Python function with a user interface. In the example above, we saw a simple text-based function, but the function could be anything from music generator to a tax calculator to the prediction function of a pretrained machine learning model.

The core Interface class is initialized with three required parameters:

  • fn: the function to wrap a UI around
  • inputs: which component(s) to use for the input (e.g. "text", "image" or "audio")
  • outputs: which component(s) to use for the output (e.g. "text", "image" or "label")

Let's take a closer look at these components used to provide input and output.

Components Attributes

We saw some simple Textbox components in the previous examples, but what if you want to change how the UI components look or behave?

Let's say you want to customize the input text field — for example, you wanted it to be larger and have a text placeholder. If we use the actual class for Textbox instead of using the string shortcut, you have access to much more customizability through component attributes.

import gradio as gr

def greet(name):
    return "Hello " + name + "!"

demo = gr.Interface(
    fn=greet,
    inputs=gr.Textbox(lines=2, placeholder="Name Here..."),
    outputs="text",
)
demo.launch()

hello_world_2 demo

Multiple Input and Output Components

Suppose you had a more complex function, with multiple inputs and outputs. In the example below, we define a function that takes a string, boolean, and number, and returns a string and number. Take a look how you pass a list of input and output components.

import gradio as gr

def greet(name, is_morning, temperature):
    salutation = "Good morning" if is_morning else "Good evening"
    greeting = f"{salutation} {name}. It is {temperature} degrees today"
    celsius = (temperature - 32) * 5 / 9
    return greeting, round(celsius, 2)

demo = gr.Interface(
    fn=greet,
    inputs=["text", "checkbox", gr.Slider(0, 100)],
    outputs=["text", "number"],
)
demo.launch()

hello_world_3 demo

You simply wrap the components in a list. Each component in the inputs list corresponds to one of the parameters of the function, in order. Each component in the outputs list corresponds to one of the values returned by the function, again in order.

An Image Example

Gradio supports many types of components, such as Image, DataFrame, Video, or Label. Let's try an image-to-image function to get a feel for these!

import numpy as np
import gradio as gr

def sepia(input_img):
    sepia_filter = np.array([
        [0.393, 0.769, 0.189], 
        [0.349, 0.686, 0.168], 
        [0.272, 0.534, 0.131]
    ])
    sepia_img = input_img.dot(sepia_filter.T)
    sepia_img /= sepia_img.max()
    return sepia_img

demo = gr.Interface(sepia, gr.Image(shape=(200, 200)), "image")
demo.launch()

sepia_filter demo

When using the Image component as input, your function will receive a NumPy array with the shape (height, width, 3), where the last dimension represents the RGB values. We'll return an image as well in the form of a NumPy array.

You can also set the datatype used by the component with the type= keyword argument. For example, if you wanted your function to take a file path to an image instead of a NumPy array, the input Image component could be written as:

gr.Image(type="filepath", shape=...)

Also note that our input Image component comes with an edit button 🖉, which allows for cropping and zooming into images. Manipulating images in this way can help reveal biases or hidden flaws in a machine learning model!

You can read more about the many components and how to use them in the Gradio docs.

Chatbots

Gradio includes a high-level class, gr.ChatInterface, which is similar to gr.Interface, but is specifically designed for chatbot UIs. The gr.ChatInterface class also wraps a function but this function must have a specific signature. The function should take two arguments: message and then history (the arguments can be named anything, but must be in this order)

  • message: a str representing the user's input
  • history: a list of list representing the conversations up until that point. Each inner list consists of two str representing a pair: [user input, bot response].

Your function should return a single string response, which is the bot's response to the particular user input message.

Other than that, gr.ChatInterface has no required parameters (though several are available for customization of the UI).

Here's a toy example:

import random
import gradio as gr

def random_response(message, history):
    return random.choice(["Yes", "No"])

demo = gr.ChatInterface(random_response)

demo.launch()

chatinterface_random_response demo

You can read more about gr.ChatInterface here.

Blocks: More Flexibility and Control

Gradio offers two approaches to build apps:

1. Interface and ChatInterface, which provide a high-level abstraction for creating demos that we've been discussing so far.

2. Blocks, a low-level API for designing web apps with more flexible layouts and data flows. Blocks allows you to do things like feature multiple data flows and demos, control where components appear on the page, handle complex data flows (e.g. outputs can serve as inputs to other functions), and update properties/visibility of components based on user interaction — still all in Python. If this customizability is what you need, try Blocks instead!

Hello, Blocks

Let's take a look at a simple example. Note how the API here differs from Interface.

import gradio as gr

def greet(name):
    return "Hello " + name + "!"

with gr.Blocks() as demo:
    name = gr.Textbox(label="Name")
    output = gr.Textbox(label="Output Box")
    greet_btn = gr.Button("Greet")
    greet_btn.click(fn=greet, inputs=name, outputs=output, api_name="greet")

demo.launch()

hello_blocks demo

Things to note:

  • Blocks are made with a with clause, and any component created inside this clause is automatically added to the app.
  • Components appear vertically in the app in the order they are created. (Later we will cover customizing layouts!)
  • A Button was created, and then a click event-listener was added to this button. The API for this should look familiar! Like an Interface, the click method takes a Python function, input components, and output components.

More Complexity

Here's an app to give you a taste of what's possible with Blocks:

import numpy as np
import gradio as gr


def flip_text(x):
    return x[::-1]


def flip_image(x):
    return np.fliplr(x)


with gr.Blocks() as demo:
    gr.Markdown("Flip text or image files using this demo.")
    with gr.Tab("Flip Text"):
        text_input = gr.Textbox()
        text_output = gr.Textbox()
        text_button = gr.Button("Flip")
    with gr.Tab("Flip Image"):
        with gr.Row():
            image_input = gr.Image()
            image_output = gr.Image()
        image_button = gr.Button("Flip")

    with gr.Accordion("Open for More!"):
        gr.Markdown("Look at me...")

    text_button.click(flip_text, inputs=text_input, outputs=text_output)
    image_button.click(flip_image, inputs=image_input, outputs=image_output)

demo.launch()

blocks_flipper demo

A lot more going on here! We'll cover how to create complex Blocks apps like this in the building with blocks section for you.

Congrats, you're now familiar with the basics of Gradio! 🥳 Go to our next guide to learn more about the key features of Gradio.

Open Source Stack

Gradio is built with many wonderful open-source libraries, please support them as well!

huggingface python fastapi encode svelte vite pnpm tailwind storybook chromatic

License

Gradio is licensed under the Apache License 2.0 found in the LICENSE file in the root directory of this repository.

Citation

Also check out the paper Gradio: Hassle-Free Sharing and Testing of ML Models in the Wild, ICML HILL 2019, and please cite it if you use Gradio in your work.

@article{abid2019gradio,
  title = {Gradio: Hassle-Free Sharing and Testing of ML Models in the Wild},
  author = {Abid, Abubakar and Abdalla, Ali and Abid, Ali and Khan, Dawood and Alfozan, Abdulrahman and Zou, James},
  journal = {arXiv preprint arXiv:1906.02569},
  year = {2019},
}