Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

renv

By renv · rstudio.github.io

  • Free plan
  • Windows
  • macOS
  • Linux
7.9 Club score Visit rstudio.github.io

What renv is

renv is a free, MIT-licensed tool for creating isolated, portable, reproducible environments for R projects. Each project receives a private library, so package changes stay separate from other projects. renv records package versions and metadata in an renv.lock file that collaborators can use to restore dependencies elsewhere. The documented workflow uses init() to set up a project, snapshot() to record packages, and restore() to reinstall them. It installs and updates packages from CRAN and GitHub, and can manage a project-local Python environment alongside R dependencies. A package cache can speed installations across projects. Guides cover GitHub Actions, GitLab CI, Docker, and Posit Connect. With Posit Package Manager, renv::vulns() can check dependencies for known vulnerabilities. It supports Windows, macOS, and Linux, plus private registry authentication and offline installation. System libraries and operating-system details remain outside the lockfile.

Who it suits

renv suits R developers, data teams, and collaborators who need repeatable project dependencies across Windows, macOS, or Linux. It also fits R projects using Python packages or CI and Docker workflows.

Good to know, and what to watch

  • Private library for each project
  • Lockfile restores recorded dependencies
  • Supports R and project-local Python packages
  • Works with CI, Docker, and Posit Connect
  • Free and MIT licensed
  • System libraries are outside renv’s lockfile
  • Static analysis may miss package usage
  • Docker may be needed for system reproducibility

renv

Free

Free plan

The verdict

renv gives R projects a structured way to isolate and restore package environments. Its lockfile and integrations help with collaboration, while full runtime reproducibility still depends on system-level factors.

What the maker publishes

CI integrations
The CI guide covers GitHub Actions and GitLab CI workflows for restoring project libraries from the lockfile. source
Dependency discovery limit
By default, a package must be installed in the project library and detected as used by the project to be recorded in the lockfile; static analysis may not recognize every way a package is used. source
Dependency resolution
Yes source
Docker
The Docker guide explains using renv with containers to fix both the underlying system and required R packages for an application. source
Founded
2019 source
Free plan
Yes source
License
renv is distributed under the MIT license. source
Lockfile
renv records package versions and metadata in a renv.lock file so they can be reinstalled elsewhere. source
Lockfiles
renv records package versions and metadata in renv.lock, which collaborators can use to restore project dependencies. source
Lockfile support
Yes source
Offline installation
Yes source
Package cache
renv uses a cache to make installing and updating packages across multiple projects faster. source
Package formats
R packages; Python packages source
Package sources
The overview describes installing and updating packages from CRAN and GitHub. source
Package sources
renv supports packages from CRAN, GitHub, Bioconductor, custom repositories, and a local package cellar. source
Posit Connect
renv can manage the local project environment for content published to Posit Connect, which recreates and manages the deployment environment. source
Private registry auth
Yes source
Project libraries
Each project gets a private library, so installing or updating a package for one project does not affect other projects. source
Purpose
renv helps create isolated, portable, reproducible environments for R projects. source
Python integration
For R projects that also use Python packages, renv can manage a project-local Python environment and track Python dependencies alongside R packages. source
Reproducibility limit
The documentation notes that operating systems, compiler flags, and system libraries can still affect runtime behavior, and recommends Docker to capture these aspects. source
Support
The project directs questions to its FAQ and Posit Forum, and bug reports to its GitHub issue tracker. source
Supported platforms
Windows,macOS,Linux source
System reproducibility limit
The Docker guide notes that operating system, compiler flags, numerical libraries, and system libraries can affect runtime behavior beyond the R library state captured by renv. source

Checked against the maker's pages on 9 Oct 2026.