Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Data & Science›.rdata
THE FILE FIELD GUIDE
.rdata

R Workspace

Data & Science

RDATA saves collections of named R objects. load can overwrite same-named workspace variables; preserve current work and use a separate restore environment. It does not necessarily include all packages or external resources.

What it is used for
Saving a collection of named R objects
What the file contains
Binary data
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

Load into a separate environment

Protect existing same-name objects.

  1. Verify trusted provenance and producer R version.
  2. Create a separate environment and pass it to load via envir.
  3. Inspect restored names and object structures.
Inspect the required restored objects

RData need not represent one table.

  1. Inspect the names returned by loading.
  2. Inspect classes/structures to distinguish tables, models and lists.
  3. Extract required values separately and compare them with expectations.
Prepare an organized handover

Select required objects and environment information.

  1. Confirm required objects and packages.
  2. Save separately as single-object RDS or appropriate tabular output.
  3. Reopen and compare names, classes and values.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Variables changed: separate restore destination and preserve work.
  • Package warnings: check producer versions and class definitions.
  • Confused with RDS: identify the save method and matching reader.
  • Existing objects replaced: inspect load’s destination environment.
  • Expected table absent: inspect restored names and classes.
  • Model does not work: inspect dependencies and producer environment.

RDATA → selected RDS / CSV

  1. Restore separately and identify target names/types.
  2. Use saveRDS for one object or table export for data; compare values/attributes.
  3. Record restored names and validate the selected-object output after reopening.

Reproduction may still need code/packages; CSV does not retain functions, environments or classes.

Specify the destination environment

load restores named objects and can replace existing values; use a dedicated inspection environment.

Source for these steps：R Core Team · Reload Saved Datasets / R Core Team · Serialization Interface for Single Objects

Do not treat an entire workspace as a table

A workspace can contain multiple tables, models or other objects; identify required targets/dependencies.

Validate dates, factors, missing values and types in table output and retain RData.

Source for these steps：R Core Team · Reload Saved Datasets / R Core Team · Serialization Interface for Single Objects

Related-format differences

Related-format differences
FormatMain roleWhat to check
RDataNamed objectsDedicated load environment
RDSSingle objectChoose assignment name
CSVText tableType/attribute differences

Handling and security

Preserve originals/work; do not run unknown functions. A separate R environment avoids name collisions, not malicious execution.

Questions and answers

Does it always contain everything?

Only the objects selected when saving.

Can load overwrite variables?

Yes, in its target environment.

Can renaming interchange RDS/RDATA?

Their read/write methods differ.

Does the filename become the variable name?

Stored object names are restored; inspect the list returned by load.

Can several restored tables become one CSV?

Define required joins from table relationships; serialization is not automatic tabular merging.

Format facts: name, steward and MIME type
Formal name
R saved object collection / workspace image
Steward / specification
R Core Team
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources