Skip to content

Settings Backup, Import, and Export

OpenScreech provides three related transfer paths. Choose the narrowest one that matches what you need:

Transfer Format What It Carries Import Behavior
Export All Settings… Property list (.plist) All persistent OpenScreech app settings Replaces the destination installation's saved settings
LLM Processor Library Export… JSON The selected reusable LLM processor Adds the imported processor to the library
Profiles Export… JSON Selected profiles and the LLM processors referenced by their stages Adds selected profiles and their required processors

Sensitive Information

Transfer files are not encrypted. Depending on what you configured, they can contain:

  • API keys
  • HTTP tokens and authorization headers
  • enabled and disabled OpenAI-compatible Custom Header names and values
  • endpoint URLs and model names
  • System Prompt text and the Send system prompt setting
  • Trigger Routing request headers and payload templates
  • HTTP service and other integration configuration

Request previews redact common credential-style headers, but export files preserve the real values so an imported configuration can continue to work. Store exports and automatic rollback backups as securely as you would store the credentials themselves. Review a file before sharing it with another person or attaching it to a support request.

Export All Settings

Open App Settings → Settings Backup & Transfer and choose Export All Settings….

The full export includes persistent OpenScreech configuration such as:

  • profiles and their processing graphs
  • reusable LLM processors, including prompts, prompt-delivery choices, API keys, and Custom Headers
  • hotkeys and reusable rule libraries
  • recording, file-transcription, HTTP service, Notes, and app preferences
  • selected model, voice, output, and folder settings

It does not include:

  • downloaded speech recognition, diarisation, text-to-speech model, or voice files
  • recordings, Notes, saved transcripts, temporary history, or temporary Screechback audio
  • macOS Microphone, Accessibility, or Input Monitoring permissions
  • the macOS Start OpenScreech when you log in registration

On a new Mac, download the required local models again and re-enable the required macOS permissions and login setting.

Import All Settings

Import All Settings… replaces the destination installation's persistent OpenScreech settings rather than merging individual entries. Finish active recording and file-transcription work first. After a successful import, OpenScreech quits so the restored configuration can load cleanly when reopened.

Create rollback backup before importing is enabled by default. The backup captures the settings that existed immediately before replacement and may contain the same sensitive credentials described above. Use Show in Finder to inspect the configured backup folder.

LLM Processor Import and Export

The LLM Post-Processing Library's Export… action writes the selected processor. Its JSON includes:

  • provider, endpoint, and model
  • System Prompt text and Send system prompt
  • API key
  • every Custom Header's name, value, and enabled state
  • timeout and transcript-wrapping settings

Import… adds the processor to the current library. It does not download a model or validate that the destination can reach the configured endpoint. Test the imported processor and review its credentials before using it in a workflow.

Profile Import and Export

A profile export bundles the selected profiles and every reusable LLM processor referenced by their graph stages. Bundled processors retain their complete configuration, including API keys and Custom Headers. This makes the profile portable, but it also means a seemingly ordinary profile JSON can contain credentials.

Profile import merges selected profiles into the existing profile list. Re-check quick-switch keys, referenced libraries, processor credentials, local model availability, folders, and permissions on the destination Mac.

Safe Transfer Checklist

  1. Use the narrowest export that contains what you need.
  2. Assume the export contains secrets unless you have inspected it.
  3. Transfer it through a secure channel and avoid public issue attachments.
  4. Delete unnecessary copies after the import succeeds.
  5. Reopen OpenScreech and test the affected processor or profile.
  6. Rotate credentials if an export was shared with the wrong person or stored insecurely.

See Also