Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time


πŸ“… Create interactive timeline visualizations in R

Demo Β· by Dean Attali

R build status CRAN version

{timevis} lets you create rich and fully interactive timeline visualizations in R. Timelines can be included in Shiny apps or R markdown documents. {timevis} includes an extensive API to manipulate a timeline after creation, and supports getting data out of the visualization into R. This package is based on the visjs Timeline JavaScript library.

Need Shiny help? I'm available for consulting.
If you find {timevis} useful, please consider supporting my work! ❀

This package is part of a larger ecosystem of packages with a shared vision: solving common Shiny issues and improving Shiny apps with minimal effort, minimal code changes, and clear documentation. Other packages for your Shiny apps:

Package Description Demo
shinyjs πŸ’‘ Easily improve the user experience of your Shiny apps in seconds πŸ”—
shinyalert πŸ—―οΈ Easily create pretty popup messages (modals) in Shiny πŸ”—
shinyscreenshot πŸ“· Capture screenshots of entire pages or parts of pages in Shiny apps πŸ”—
shinycssloaders βŒ› Add loading animations to a Shiny output while it's recalculating πŸ”—
colourpicker 🎨 A colour picker tool for Shiny and for selecting colours in plots πŸ”—
shinybrowser 🌐 Find out information about a user's web browser in Shiny apps πŸ”—
shinydisconnect πŸ”Œ Show a nice message when a Shiny app disconnects or errors πŸ”—
shinytip πŸ’¬ Simple flexible tooltips for Shiny apps WIP
shinymixpanel πŸ” Track user interactions with Mixpanel in Shiny apps or R scripts WIP
shinyforms πŸ“ Easily create questionnaire-type forms with Shiny WIP


Click here to view an interactive demo of many {timevis} features.

If you create a cool timeline with {timevis}, I’d love to hear about it!

Sponsors πŸ†

There are no sponsors yet

Become the first sponsor for {timevis}!

Table of contents


For most users: To install the stable CRAN version:


For advanced users: To install the latest development version from GitHub:


How to use

You can view a minimal timeline without any data by simply running


Minimal timeline

You can add data to the timeline by supplying a data.frame

data <- data.frame(
  id      = 1:4,
  content = c("Item one"  , "Item two"  ,"Ranged item", "Item four"),
  start   = c("2016-01-10", "2016-01-11", "2016-01-20", "2016-02-14 15:00:00"),
  end     = c(NA          ,           NA, "2016-02-04", NA)


Basic timeline

Every item must have a content and a start variable. If the item is a time range rather than a single point in time, you can supply an end as well. id is only required if you want to access or manipulate an item.

There are more variables that can be used in the data.frame – they are all documented in the help file for ?timevis() under the Data format section.

By default, a timeline will show the current date as a red vertical line and will have zoom in/out buttons. You can supply many customization options to timevis() in order to get it just right (see ?timevis() for details).

Slightly more advanced examples

The content of an item can even include HTML, which makes it easy to show any kind of data in a timeline, such as the matches of the 2014 World Cup:

World cup timeline

If you know some CSS, you can completely customize the look of the timeline:

Custom style timeline


The timeline lets the user interact with it seamlessly. You can click on the zoom in/out buttons or drag the timeline left/right in order to move to past/future dates.

If you set the editable = TRUE option, then the user will be able to add new items by double clicking, modify items by dragging, and delete items by selecting them.


You can use the groups feature to group together multiple items into "buckets". When using groups, all items with the same group are placed on one line. A vertical axis is displayed showing the group names. Grouping items can be useful for a wide range of applications, for example when showing availability of multiple people, rooms, or other resources next to each other. You can also think of groups as "adding a Y axis".

Here is an example of a timeline that has four groups: "Gym", "Pool", "Sauna", "Hot Tub":

Groups timeline

In order to use groups, items in the data need to have group ids, and a separate dataframe containing the group information needs to be provided. More information about using groups is available in the help file for ?timevis() under the Groups section.

Groups can also contain nested groups. The next example is similar to the previous one, except "Sauna" and "Hot Tub" are now nested under "Pool":

Nested groups timeline

Refer to the visjs Timeline documentation to see all the options that are supported.

Functions to manipulate a timeline

There are many functions that allow programmatic manipulation of a timeline. For example: addItem() programmatically adds a new item, centerItem() moves the timeline so that a given item is centered, setWindow() sets the start and end dates of the timeline, setOptions() updates the configuration options, and many more functions are available.

There are two ways to call these timeline manipulation functions:

1. Timeline manipulation using %>% on timevis()

You can manipulate a timeline widget during its creation by chaining functions to the timevis() call. For example:

timevis() %>%
  addItem(list(id = "item1", content = "one", start = "2016-08-01")) %>%

This method of manipulating a timeline is especially useful when creating timeline widgets in the R console or in R markdown documents because it can be used directly when initializing the widget.

2. Timeline manipulation using a timeline’s ID

In Shiny apps, you can manipulate a timeline widget at any point after its creation by referring to its ID. For example:


ui <- fluidPage(
  actionButton("btn", "Add item and center")

server <- function(input, output, session) {
  output$mytime <- renderTimevis(timevis())
  observeEvent(input$btn, {
    addItem("mytime", list(id = "item1", content = "one", start = "2016-08-01"))
    centerItem("mytime", "item1")

shinyApp(ui = ui, server = server)

You can even chain these functions and use this manipulation code instead of the bold code:

addItem("mytime", list(id = "item1", content = "one", start = "2016-08-01")) %>%

Technical note: If you’re trying to understand how both methods of timeline manipulation work, it might seem very bizarre to you. The reason they work is that every manipulation function accepts either a timevis object or the ID of one. In order to make chaining work, the return value from these functions depend on the input: if a timevis object was given, then an updated timevis object is returned, and if an ID was given, then the same ID is returned.

Extending timevis

If you need to perform any actions on the timeline object that are not supported by the {timevis} API, you may be able to do so by manipulating the timeline's JavaScript object directly. The timeline object is available via document.getElementById("id").widget.timeline (replace id with the timeline's id).

This timeline object is the direct widget that vis.js creates, and you can see the visjs documentation to see what actions you can perform on that object.

In a Shiny app

You can add a timeline to a Shiny app by adding timevisOutput() to the UI and renderTimevis(timevis()) to the server.

Retrieving data from the widget

It is possible to retrieve data from a timeline in a Shiny app. When a timeline widget is created in a Shiny app, there are four pieces of information that are always accessible as Shiny inputs. These inputs have special names based on the timeline’s id. Suppose that a timeline is created with an outputId of "mytime", then the following four input variables will be available:

  • input$mytime_data - will return a data.frame containing the data of the items in the timeline. The input is updated every time an item is modified, added, or removed.
  • input$mytime_ids - will return the IDs (a vector) of all the items in the timeline. The input is updated every time an item is added or removed from the timeline.
  • input$mytime_selected - will return the IDs (a vector) of the selected items in the timeline. The input is updated every time an item is selected or unselected by the user. Note that this will not get updated if an item is selected programmatically using the API functions.
  • input$mytime_window - will return a 2-element vector containing the minimum and maximum dates currently visible in the timeline. The input is updated every time the viewable window of dates is updated (by zooming or moving the window).
  • input$mytime_visible - will return a list of IDs of items currently visible in the timeline.

Crosstalk support

{timevis} is fully compatible with crosstalk. This means that you can provide it with a crosstalk SharedData object to select/filter data across multiple Shiny widgets.

Here is a simple example:

df <- data.frame(start = c(Sys.Date(), Sys.Date() - 1, Sys.Date() - 2), content = 1:3)
shared_df <- crosstalk::SharedData$new(df)
  timevis(shared_df, options = list(multiselect = TRUE), showZoom = FALSE, width = "100%"),

If you select any events in the timeline (use ctrl or shift to select multiple events), then the table will automatically select those as well, and vice versa.

You can view examples of many of the features supported by checking out the demo Shiny app. If you want to see how those examples were created, the full code for the examples is inside inst/example.

Lastly, if you want to learn how to develop an htmlwidget to have similar features as this package, you can check out the timevisBasic package or my tutorial on htmlwidgets tips.


Logo design by Alfredo HernΓ‘ndez.