Data Types

Supported Data Types

h5lite supports reading and writing a wide range of R data types. The table below lists the default mapping when writing to HDF5.

Dimensions: Scalars, Vectors, and Arrays

Atomic data types (Integer, integer64, Double, Logical, Character, Complex, Raw, and POSIXt) can be written to HDF5 as scalars, 1D vectors, or N-dimensional arrays.

• Scalars: To write a single value as a true HDF5 scalar (0 dimensions), you must wrap the value in I().
• Vectors: Standard R vectors are written as 1D arrays (Simple Dataspace with rank 1).
• Arrays/Matrices: R objects with dim attributes are written as N-dimensional datasets, preserving their shape.

# 1. Scalar (0 dims)
h5_write(I(42), file, "structure/scalar")

# 2. Vector (1 dim)
h5_write(c(1, 2, 3), file, "structure/vector")

# 3. Matrix (2 dims)
h5_write(matrix(1:9, 3, 3), file, "structure/matrix")

For more complex dimensional structures, refer to vignette('matrices').

Numeric Data

R uses 32-bit integers and 64-bit doubles. When writing with as = "auto", h5lite analyzes the range of your data to select the most compact HDF5 type.

• Default: Selects optimal type based on range of values.
• With NA: float64 (H5T_IEEE_F64LE)
• Fractional Values: Double-precision vectors with fractional values default to float64.
• Coercion: You can override this using int[8|16|32|64], uint[8|16|32|64], float[16|32|64], or bfloat16.

# Integers between 0 and 255 (uint8)
h5_write(c(1L, 2L, 3L), file, "integers/small")

# Integers with NA -> float64
h5_write(c(1L, NA, 3L), file, "integers/with_na")

# Force larger type (int16)
h5_write(1:100, file, "integers/short", as = "int16")

64-bit Integers (integer64)

• Default: int64 (H5T_STD_I64LE)
• Coercion: none

R does not natively support 64-bit integers, but h5lite supports reading and writing them via the bit64 package.

if (requireNamespace("bit64", quietly = TRUE)) {
  val <- bit64::as.integer64(c("9223372036854775807", "-9223372036854775807"))
  h5_write(val, file, "integers/int64")
}

Double (Numeric) Data

R’s default numeric type is double-precision.

• Default: float64 (H5T_IEEE_F64LE)
• Coercion: int[8|16|32|64], uint[8|16|32|64], float[16|32|64], or bfloat16

data <- rnorm(10)

# Default (float64)
h5_write(data, file, "doubles/default")

# Single Precision (float32) - Saves 50% space
h5_write(data, file, "doubles/float32", as = "float32")

Logical Data

• Default: uint8 (H5T_STD_U8LE)
• With NA: float64 (H5T_IEEE_F64LE)
• Coercion: int[8|16|32|64], uint[8|16|32|64], float[16|32|64], or bfloat16

bools <- sample(c(TRUE, FALSE), 1000, replace = TRUE)

h5_write(bools, file, "logicals/packed")

Character Data

HDF5 supports two methods for storing strings. By default (as = "auto"), h5lite chooses the best approach:

• Variable-Length: Used if the vector contains NA or if string lengths are highly inconsistent.
• Fixed-Length: Used for short, consistent strings without NA to allow for compression.

# UTF-8 variable length
h5_write(c("apple", "banana", NA), file, "strings/var_utf8")

# ASCII variable length
h5_write(c("A", "B", "C"), file, "strings/var_ascii", as = "ascii")

# UTF-8 auto-detected fixed length
h5_write(c("apple", "banana"), file, "strings/fixed_utf8")

# ASCII fixed length (1 byte)
h5_write(c("A", "B", "C"), file, "strings/fixed_ascii", as = "ascii[1]")

Dates and Times (POSIXt)

R date-time objects (POSIXct / POSIXlt) are stored as Strings in ISO 8601 format, converted to UTC (YYYY-MM-DDTHH:MM:SSZ). Fractional seconds are kept, to the microsecond, when present (for example 2024-01-01T12:00:00.75Z). This ensures maximum portability with other languages and HDF5 tools that do not share R’s specific epoch-based integer representation.

now <- Sys.time()
h5_write(now, file, "datetime/iso8601")

Complex Data

R complex numbers are written using the new complex floating-point type introduced in HDF5 2.0.0 (H5T_COMPLEX_IEEE_F64LE).

Compatibility Warning: This data type for complex numbers is a feature specific to HDF5 version 2.0+. Datasets written with this type generally cannot be read by HDF5 readers built against older versions of the library (e.g., HDF5 1.10 or 1.12). Ensure that any downstream tools or libraries used to read these files are updated to support HDF5 2.0 standards.

comp <- c(1+2i, 3+4i)
h5_write(comp, file, "complex_data")

Raw Data

Raw vectors (bytes) are stored as HDF5 OPAQUE types. This is ideal for storing binary blobs, images, or serialized objects where you need to preserve the exact byte sequence without interpretation.

raw_vec <- as.raw(c(0x01, 0xFF, 0x1A))
h5_write(raw_vec, file, "binary_blob")

Factors

R Factors are stored as HDF5 ENUM types. This maps the integer codes to the factor levels (labels) efficiently within the file header, ensuring the labels are preserved without duplicating string data for every element.

fac <- factor(c("low", "high", "medium", "low"))
h5_write(fac, file, "categorical")

Lists

R lists are mapped to HDF5 Groups. Since lists are recursive containers, h5lite walks the list and creates a dataset (or subgroup) for every element found. You can use as = c("element_name" = "skip") to exclude specific items.

my_list <- list(data = 1:100, meta = list(valid = TRUE))
h5_write(my_list, file, "types/list")

Data Frames

Data Frames are stored as HDF5 Compound types (tables). This ensures that rows are kept together in memory. You can use the as argument to specify the type of individual columns.

For a comprehensive guide, see vignette('data-frames').

df <- data.frame(
  id = 1:5,
  score = c(10.5, 20.2, 15.0, 9.8, 30.1)
)

# 1. 'id' coerced to uint16
# 2. 'score' coerced to float32
h5_write(df, file, "types/dataframe", as = c(
  "id"    = "uint16",
  "score" = "float32"
))

NULL

The NULL object in R is mapped to a dataset with a NULL Dataspace (H5S_NULL). This creates a dataset that exists in the file structure but contains no data elements and consumes no storage space.

h5_write(NULL, file, "placeholders/empty_slot")

Data Types and Compression

Every dataset is compressed by default (gzip level 5 with byte shuffling), and the storage type you choose affects how well it compresses:

• Smaller types mean less data. Storing doubles as float32 halves their size before compression even starts. The compact integer types that as = "auto" picks save space the same way.
• Fixed-length strings compress. Variable-length strings don’t. If text makes up much of your data, use as = "utf8[]" when there are no NA values.
• ZFP needs 32- or 64-bit numeric types. If you use the ZFP codec on whole numbers, set as = "int32", "int64", "float32", or "float64" explicitly. Otherwise h5lite falls back to gzip.

h5_write(rnorm(1000), file, "compressed/zstd", as = "float32", compress = "zstd-5")

For codec choices, lossy compression, chunk sizing, and inspecting the results, see vignette('compression').