v1.51

Memory

The memory backend is an in RAM backend. It does not persist its data - use the local backend for that.

The memory backend behaves like a bucket-based remote (e.g. like s3). Because it has no parameters you can just use it with the :memory: remote name.

Configuration

You can configure it as a remote like this with rclone config too if you want to:

  1. No remotes found, make a new one?
  2. n) New remote
  3. s) Set configuration password
  4. q) Quit config
  5. n/s/q> n
  6. name> remote
  7. Type of storage to configure.
  8. Enter a string value. Press Enter for the default ("").
  9. Choose a number from below, or type in your own value
  10. [snip]
  11. XX / Memory
  12.    \ "memory"
  13. [snip]
  14. Storage> memory
  15. ** See help for memory backend at: https://rclone.org/memory/ **
  17. Remote config
  19. Configuration complete.
  20. Options:
  21. - type: memory
  22. Keep this "remote" remote?
  23. y) Yes this is OK (default)
  24. e) Edit this remote
  25. d) Delete this remote
  26. y/e/d> y

Because the memory backend isn’t persistent it is most useful for testing or with an rclone server or rclone mount, e.g.

  1. rclone mount :memory: /mnt/tmp
  2. rclone serve webdav :memory:
  3. rclone serve sftp :memory:

Modification times and hashes

The memory backend supports MD5 hashes and modification times accurate to 1 nS.

Restricted filename characters

The memory backend replaces the default restricted characters set.

Advanced options

Here are the Advanced options specific to memory (In memory object storage system.).

--memory-description

Description of the remote.

Properties:

  • Config: description
  • Env Var: RCLONE_MEMORY_DESCRIPTION
  • Type: string
  • Required: false