Privacy

When to use local processing or a Cloud copy

MD.SAVE writing, conversion, and download, TAB.REC recording, and PDF.ABLE PDF work can finish locally. You can manually keep a copy in MD.SAVE Cloud Beta when you need to find it on another device, but it does not add automatic saving or collaboration.

Written by: PackWink operator · reproduced in the public release
Last checked: 2026-08-30
Reading time: 7 min read

ResultA processing choice that matches the material and the way people work

Local processing fits

One-time document conversion followed by a file download
Meeting or lecture audio that does not need a server
Contracts and reports that need PDF viewing, merging, or splitting without an upload
A task that should begin without an account or team permission
Clipboard text and filenames that should not enter analytics

Cloud processing may fit better

Several people must edit at the same time
Automatic recovery after device loss is mandatory
An organization needs central retention and access logs
The same project must continue across phone and work computer

Local is not a backup

Browser storage still depends on device space, browser settings, and user deletion. Export important TAB.REC work as regular audio and a .tabrec project. MD.SAVE local work needs no sign-in or upload, but Cloud Beta is not automatic saving or sync. Keep a local .md copy of important documents.

MD.SAVE Cloud Beta runs only when you save a copy

After signing in with ChatGPT, only the Markdown for which you choose ‘Save a copy to Cloud’ is uploaded. Writing, converting, reading, and downloading locally do not trigger a Cloud API call.

Cloud Beta provides document search, folders, tags, trash, downloads, and full export. It does not provide collaborative editing, shared links, comments, version history, or automatic recovery. Keep a separate local copy of important documents while storage durability remains in beta.

What PackWink processes

MD.SAVE local work handles pasted text, filenames, and conversion in the browser
MD.SAVE Cloud Beta stores only a Markdown copy you save manually and the metadata needed to organize it
TAB.REC keeps audio recorded from the selected Chrome tab, notes, saved times, and user-triggered screenshots on the device
TAB.REC Studio analyzes selected audio and .tabrec projects locally
PDF.ABLE reads, merges, splits, and converts the PDFs and images you choose in the browser
Product analytics do not include document source, PDF contents, audio, notes, or file contents

Four questions before choosing

Can this task finish without a server upload?
Must it recover after this device is gone?
Will people edit it concurrently?
Does an organization mandate storage location and retention?