---
name: "hpcopy"
section: "1"
platform: "linux"
package: "hfsplus"
version: "1.0.4-19"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/hpcopy"
---

# hpcopy(1)

copy files from an HFS+ volume

## NAME

hpcopy — copy files from an HFS+ volume

## SYNOPSIS

**hpcopy** \[**-m**  \| **-b**  \| **-t**  \| **-r**  \| **-a** \] *source-path* ... *target-path*

## Description

**hpcopy** copies files and directories from an  HFS+ volume.  If multiple files are to be copied, the target  path must be a directory.

Since Macintosh files contain two forks, which are not  representably in Unix file systems, copies use one of several  translation modes:

- **-m**

  **Mac Binary II** is a format for  binary file transfer.  Both forks of the Macintosh file  are preserved.  This is the recommended mode for  transferring arbitrary Macintosh files.

- **-b**

  **BinHex** also preserves both  forks of the Macintosh file.  In addition, the encoded  file contains only ASCII characters, making it suitable  for electronic mail transmission.

- **-t**

  **Text** copies only the data fork  of the Macintosh file, while the contents of the resource  fork are lost.  In addition, this mode translates  end-of-line characters.  This translation should be used  for text files.

- **-r**

  **Raw Data** copies only the data  fork of the Macintosh file, while the contents of the  resource fork are lost.

- **-a**

  **Automatic** mode applies a set of  predefined heuristics to determine the appropriate  translation.  This is the default if no mode is specified.

## See also

[hfsplus(7)](/hfsplus/7.md), [hpmount(1)](/hpmount/1.md), [hpls(1)](/hpls/1.md), [hpcd(1)](/hpcd/1.md), [hprm(1)](/hprm/1.md), [hpmkdir(1)](/hpmkdir/1.md), [hppwd(1)](/hppwd/1.md), [hpumount(1)](/hpumount/1.md), [hpfsck(1)](/hpfsck/1.md).

## Author

This manual page was written by Jens Schmalzing  \<jensen@debian.org\> for **Debian GNU/Linux** using the  manual page by Klaus Halfmann  \<halfmann@libra.de\> that comes with the  source code and documentation from the **Tech Info**  **Library**.