Dashboards with Shiny for R

Quarto 1.4 Feature

This feature is new in Quarto 1.4. Download the latest version of Quarto at the download page


The Shiny package provides an easy way to build web applications with R. Quarto dashboards can include embedded Shiny components (e.g. a plot with sliders that control its inputs).

This section covers integrating Shiny with Quarto and assumes that you already have basic familiarity with Shiny. To learn more about Shiny please visit https://shiny.posit.co/r/getstarted/shiny-basics/lesson1/index.html. If you are using Python rather than R, see the documentation on using Shiny for Python.


Here we’ll explore an in-depth example that covers many of the techniques you’ll use when creating dashboards with Shiny, including factoring out setup code, reactive calculations, and more advanced layout constructs like sidebars and tabsets. Here is the interactive document we’ll be building:

Screenshot of a Diamonds Explorer App. The navigation bar shows two pages: Plot (active), and Data. On the left a sidebar contains eight inputs: a sample size slider; two checkboxes for Jitter and Smooth (both checked); and a dropdown for each of X, Y, Color, Facet Row and Facet Col. On the right, a plot of cut versus carat using points colored by clarity.

Here is the source code for this dashboard (click on the numbers on the far right for additional explanation of syntax and mechanics):

title: "Diamonds Explorer"
author: "Barkamian Analytics"
format: dashboard
server: shiny

#| context: setup
dataset <- diamonds

# {.sidebar}

sliderInput('sampleSize', 'Sample Size', 
            min=1, max=nrow(dataset),
            value=min(1000, nrow(dataset)), 
            step=500, round=0)
checkboxInput('jitter', 'Jitter')
checkboxInput('smooth', 'Smooth')

selectInput('x', 'X', names(dataset)) 
selectInput('y', 'Y', names(dataset), names(dataset)[[2]])
selectInput('color', 'Color', c('None', names(dataset)))

selectInput('facet_row', 'Facet Row',
  c(None='.', names(diamonds[sapply(diamonds, is.factor)])))
selectInput('facet_col', 'Facet Column',
  c(None='.', names(diamonds[sapply(diamonds, is.factor)])))

# Plot


# Data


#| context: server

dataset <- reactive({
  diamonds[sample(nrow(diamonds), input$sampleSize),]
output$plot <- renderPlot({
  p <- ggplot(
    aes_string(x=input$x, y=input$y)) + geom_point()
  if (input$color != 'None')
    p <- p + aes_string(color=input$color)
  facets <- paste(input$facet_row, '~', input$facet_col)
  if (facets != '. ~ .')
    p <- p + facet_grid(facets)
  if (input$jitter)
    p <- p + geom_jitter()
  if (input$smooth)
    p <- p + geom_smooth()

output$data <- renderTable({
The server: shiny option instructs Quarto to run a Shiny Server behind the document.
The context: setup cell option indicates that this code cell should run when the application starts (as opposed to when each new client session starts). Expensive initialization code (e.g. loading data) should be placed in context: setup.
Create global sidebars by adding the .sidebar class to level 1 headers. Sidebars can include code cells as well as images, narrative, and links.
These select inputs have their contents dynamically driven from the available columns in the dataset.
Level 1 headings (here # Plots and # Data) create pages within the dashboard.
Include server code (reactives that compute values or render output) in a cell with context: server.
The dataset() reactive will be called to re-sample the dataset every time the sample size changes.
The renderPlot() function regenerates the plot whenever the dataset() reactive or another input option changes.
The renderTable() function regenerates the table whenever the dataset() reactive changes.

Learning More

To learn more about Shiny for R interactive documents see the following articles:

Input Layout describes various ways to layout Shiny inputs (sidebars, input panels, attaching inputs directly to cards, etc.)

Running Documents covers how to run interactive documents both within RStudio and at the command line, as well as how to deploy them to end users.

Execution Contexts goes in depth on when different code blocks (e.g. rendering vs. serving) run as well as how to cache expensive computations for more responsive documents.

External Resources describes how to make sure that Shiny can locate resources (e.g. CSS, JS, images, etc.) that you include in your document.