ZapPad for Mac · Focused help guide

Choose text encoding

If ZapPad cannot decode a file as UTF-8 or BOM-marked UTF-16, it does not change the source. Choose an explicit legacy encoding when you know how the bytes should be interpreted, then verify the text before saving.

See the complete ZapPad manual for all menus, settings and troubleshooting. These focused guides are drawn from the same current manual.

Applies to the current Direct release documentation for Apple Silicon Macs on macOS 12 or later.

How to use this feature

Encoding and line endings

  • Use the footer’s File encoding menu to choose how the pad is written when saved. If the text contains characters the chosen encoding can’t represent, ZapPad shows an error and keeps the previous encoding.
  • To read a file in a legacy encoding, use Tools›Files and Folders›Open with Legacy Encoding… and enter Windows-1252, ISO-8859-1, Mac Roman or Shift-JIS. Only exact round trips are accepted; check the text before saving.
  • The footer’s Line endings menu (LF, CRLF, CR) converts the whole pad. Undo reverses it.

Common messages

MessageWhat to do
Pro access is required…No trial or paid coverage applies to this build. Activate a valid Direct key, refresh saved coverage or use an entitled build. Restore Purchases applies only to Apple-distributed copies. Documents remain preserved.
The document changed. Generate a new preview before applying.The pad was edited after the preview was made. Run the tool again.
Disable read-only mode before applying changes.Turn off View›Read-only.
The selection is outside the document or splits a Unicode character.Reselect the text, or select nothing to use the whole pad. Most tools need a single selection, not multiple cursors.
Enable Apple Intelligence in System Settings…Described changes need Apple Intelligence and its downloaded model. Other tools work meanwhile.
This request needs an operation outside the current … command vocabulary.Rephrase as a regex replacement, extraction, filter or supported cleanup; or use a Text tool directly.
Examples must be at most 4,000 UTF-8 bytes.Use a smaller representative sample.
Recording stopped: …An action that can’t be replayed was used. Start recording again and use keyboard edits or tools.
Changed on disk. Reload or Save As…Another app changed the file. Reload from Disk to take its version (yours stays in history), or Save As to keep both.
File access unavailable…Reopen the file with File › Open… to grant access again.
Download was incomplete. Retry to resume. / Download failed (HTTP …)Reconnect and choose Download Full Packages again; it resumes from the partial download.
The operation was cancelled.You chose Stop or Cancel, or the task was superseded. Your text is unchanged; run the command again if needed.

Frequently asked questions

Why does ZapPad say a file is not valid UTF-8?

The file contains byte sequences that cannot be decoded as UTF-8 or BOM-marked UTF-16. ZapPad leaves it unchanged instead of guessing. Use Open with Legacy Encoding and select an interpretation you trust, then inspect the text before saving.

Which legacy encodings can ZapPad open?

The encoding picker includes ISO-8859-1, Mac Roman, Shift-JIS and Windows-1252, along with UTF-8, UTF-8 BOM, UTF-16 LE and UTF-16 BE. Choose based on the file’s source; a wrong interpretation can produce unreadable characters.

Does choosing an encoding change the source file immediately?

No. Opening with an explicit encoding interprets the file for the pad. The original file is not rewritten just because you opened it. Save only after you have inspected the decoded text and intentionally choose to write the document.

For complete current feature details, open the ZapPad manual.