Contents

ChatArchive User Manual

Import and read LINE history · Search and export · Backups and privacy

Checked November 15, 2026 · Verified release 1.0.0 (1) · 2.0 interface features marked separately

Read this first: version and purpose

ChatArchive is a Mac application for keeping a readable copy of LINE conversations. It imports available history into its own local database, displays conversations and searches message text. It does not restore conversations to LINE, transfer a LINE account, send messages or recover content absent from its source.

This guide was checked on November 15, 2026. The verified release download is 1.0.0 (build 1), requiring macOS 14.0 or later. Its disk-image metadata and corresponding source were reviewed. The current Gumroad listing does not identify its delivered binary version, so its download has not been established as identical to that release.

The separate 2.0.0 (build 2) source adds features described below only where marked “If your app has the 2.0 interface.” A development version number does not establish that those features are supplied with a purchase. Check your installed app’s version in Finder’s Get Info and follow the controls you actually have.

The app interface includes English, Japanese, Traditional Chinese and Thai. This manual’s language availability is separate. Source references in this guide describe the developer’s review of a private repository; they are not public code-download links.

Install and choose the source

  1. Obtain ChatArchive from the official purchase/download channel. If supplied as a DMG, open it and copy ChatArchive to Applications before opening the application.
  2. Allow enough free Mac storage for the imported database, temporary extraction and any exports. No fixed storage allowance can cover every history.
  3. Choose between the local LINE for Mac database and a compatible LINE for iPhone iCloud backup. They can contain different periods and different numbers of messages.
  4. Before replacing an existing ChatArchive library, follow Back up and remove data.

For Mac import, install LINE for Mac, sign in through LINE and leave it running. For iCloud import, the relevant backup must be accessible through the Mac’s iCloud Drive account. ChatArchive does not provide its own LINE or Apple Account sign-in form.

The reviewed app is macOS-only. It does not read Android/Google Drive backups, ordinary Finder iPhone device backups or arbitrary ZIP files. Compatibility with every later LINE database or backup format is not guaranteed.

Import from LINE for Mac in 1.0.0

  1. Open LINE for Mac and finish signing in. Confirm that the intended account is active, then leave LINE open.
  2. In macOS System Settings → Privacy & Security → Developer Tools, allow ChatArchive if requested. This permission concerns access to the running LINE process.
  3. In ChatArchive, choose Import from LINE, then Import from LINE for Mac.
  4. Wait for detection, key retrieval, database reading and import to finish. Avoid changing accounts or quitting LINE during the operation.
  5. Check the completion counts, close the sheet and inspect several conversations and dates.

The app reads LINE’s local encrypted database using a key obtained from the running process. The source database is opened read-only. It does not ask LINE’s servers for all historical conversations. When several candidate databases exist, automatic detection prioritizes a larger database; there is no ordinary account picker here.

Full Disk Access is not a substitute for Developer Tools permission. If access or decryption fails after the documented permission is granted, contact support instead of disabling system protections. In the 2.0 interface, Mac import is hidden as a developer feature. Use the normal iCloud route there.

Import an iPhone LINE iCloud backup

This route is available in the reviewed 1.0.0 interface and is the normal route in the 2.0 interface. It reads the LINE-specific archive.zip, not a whole-device iCloud backup.

  1. Check that LINE on the iPhone has a completed, suitable Standard Backup. Follow LINE’s official backup instructions for the current phone interface.
  2. On the Mac, use the Apple Account that can access that backup and enable iCloud Drive. Allow time and an internet connection for the file to become available.
  3. Choose Import from LINE → Import from iCloud Backup.
  4. Wait for download, extraction and import. Check the resulting counts, names and dates. Later interfaces also show Imported from.

Detection looks under ~/Library/Mobile Documents/iCloud~com~linecorp~line/Data-*/Backup/archive.zip. It takes the first matching backup it finds, without a date or account selection screen; it does not promise to choose the newest one. Mac LINE does not need to be running for this route, and Developer Tools permission is not used by the iCloud reader.

What the imported history includes

The archive reflects records that exist in the selected source at import time. A successful import does not prove that every conversation ever exchanged by the account was included. Messages deleted earlier, unavailable older history and media absent from the source cannot be reconstructed.

The iCloud reader handles direct chats, multi-person chats, groups, official accounts and Keep Memo records when their expected tables are present. Names may fall back to identifiers or generic labels when contact information is missing. Unknown message types may appear as a type number.

The Mac and iCloud copies are independent sources. A phone may show history that the Mac has never stored. Importing the other source replaces the current ChatArchive library; it does not combine their coverage.

Keep the source backup separately if completeness matters. The app reads selected fields, not every LINE database table or metadata field. In particular, 2.0 reaction extraction does not incorporate SQLite journal files from the backup, so reaction completeness is not assured.

Refresh history: replacement, not accumulation

Every Mac/iCloud import replaces the entire ChatArchive contact, chat and message library. This applies to both reviewed versions. Save a separate copy before importing a newer, older or different source. There is no merge mode, incremental download or automatic scheduled synchronization.

  1. Back up the current local library and save any reading copies you need.
  2. Confirm the intended source and its backup period.
  3. Run the same import procedure again.
  4. Compare the oldest and newest dates, important conversations and completion counts with your expectations.

Import runs inside one database transaction: a database error during that transaction rolls back its changes. This is useful protection, but it is not a substitute for your backup.

Reimporting a source does not intentionally append a second copy of every existing message. It rebuilds the library from the source; duplicate records already present there may still appear. A smaller source can produce a smaller library and remove previously visible history.

Browse conversations and older messages

The left sidebar contains import, export and license controls. The middle column lists chats, ordered by their last message time. Select a chat to read it in the right column. The chat-list search box filters chat names; it does not search message bodies.

A conversation initially loads its latest 200 messages. Use Load older messages at the top to load earlier pages, up to 200 at a time. Seeing only a recent period on screen therefore does not establish that older imported messages are missing.

Messages are grouped by date and distinguish your own messages from other senders. Text can be selected and copied. In the 2.0 interface, detected links can open the system’s browser or associated application. Opening a link is a separate action from reading the local archive.

If a displayed date is implausible, preserve the source and report the version and import route. The source following 1.0.0 changes iCloud timestamp conversion, so the original release’s dates should be checked before relying on an export.

Images, attachments, stickers and reactions

Recognizing a message type is different from preserving its attachment. In 1.0.0, photos, videos, audio, files, locations, contacts and stickers are represented by text or type labels. There is no general attachment download, photo viewer or audio/video player in the reviewed interface.

If your app has the 2.0 interface

For compatible iCloud sticker records, the app reads sticker identifiers and requests a PNG from LINE’s sticker CDN. Successfully loaded images are cached locally. This is a still-image representation; animation, sound, unavailable stickers and every newer sticker format are not guaranteed.

Existing cached images can be reused offline; uncached images require a successful network request. A placeholder may indicate missing metadata, no connection or an unavailable CDN image. Importing history alone does not pre-download every sticker.

Supported reaction types can appear as emoji badges and counts from the iCloud supplementary database. These badges are not a complete record of who reacted or when. Neither stickers nor reactions make ChatArchive a full media backup.

Where your archive is stored

Imported history is stored automatically at ~/Library/Application Support/ChatArchive/chatarchive.sqlite. The normal import does not ask you to choose a database location. The database may have -wal and -shm companion files. Keep the folder together when making a backup.

In 2.0, downloaded sticker PNGs are stored in ~/Library/Application Support/ChatArchive/StickerCache/. Exports go to the location you choose in the save dialog; they are separate copies and do not update when you import again.

The local database and reading exports are not protected by ChatArchive-specific encryption or an app password. Protect them using the Mac account, device encryption and an appropriate backup destination. A file saved in a cloud-synchronized folder may be uploaded by that service.

The app’s own database is a working library, not a LINE-compatible restore package. Historical references to .chatarchive or .linearchive do not establish an available import/restore command in these reviewed Mac interfaces.

Save text copies in 1.0.0

One conversation

Select a chat and choose Save as Text above its messages. Choose the name and destination. This operation does not require an activated export license and reads all imported messages in that chat, including older pages not yet displayed.

All conversations

Choose Export All in the sidebar. An activated license is required. The reviewed 1.0.0 interface asks for a destination folder and writes a text file for each non-empty chat. In the 2.0 interface, the same sidebar operation instead saves chatarchive-export.tar.gz, containing per-chat text files.

Text output contains dates, times, sender names and stored text. It does not embed attachment binaries, sticker images or reaction badges. A non-text message with no stored text can therefore leave little useful content.

Inspect important exported conversations before relying on them. Chat names become filenames: identical names, or names that become identical after forbidden characters are replaced or long names are shortened, can collide. Save such chats separately using distinct filenames.

HTML and Markdown: only with the 2.0 interface

HTML caution: In the reviewed 2.0 implementation, HTML fragments in conversation text can affect the exported page’s behavior. Use text or Markdown instead until a corrected version has been confirmed. The steps below describe the interface, not a recommendation to open an HTML export from this implementation.

These formats are present in the reviewed 2.0 source, not in the verified 1.0.0 release interface. If your app has the Export Chat toolbar button, select a chat first, open that button, then choose a format and scope.

2.0 export choices
ChoiceLicenseOutput
Selected Chat → HTMLNo activated license requiredOne browser-readable HTML file
All Chats → HTMLActivated license requiredOne HTML file with a chat list
Markdown (ZIP)Activated license requiredAll chats as Markdown plus cached sticker files

HTML defaults to All Chats. For a single-chat export, explicitly choose Selected Chat. Save the file and wait for completion; the app opens the result using its associated application.

HTML embeds only sticker images already in the cache. View relevant stickers successfully before exporting if you need their images. Its search field filters chat names, not all message bodies, and JavaScript is required to display the conversations.

Markdown ZIP includes an attachments/stickers/ folder and Obsidian-style image references. General Markdown readers may need path or syntax adjustments. Check missing images and same-name chat files. Neither format is a complete preservation copy or an import file for LINE. Keep the database backup as well.

Purchase and activate an export license

Reading, searching and saving one chat as text are available without export activation in the reviewed code. Bulk text export requires activation. The additional 2.0 format rules are listed above. A purchase and a successful activation are separate steps.

  1. Use the current product page to check purchase and delivery details.
  2. Open Activate License in ChatArchive and enter the compatible license key supplied for the product.
  3. Activate while online and check the resulting status. Keep the purchase receipt privately.

Both reviewed versions use Lemon Squeezy’s license service, even though the later purchase link points to Gumroad. A Gumroad receipt alone does not establish that a key is compatible. If a key is missing or rejected, contact support with the order reference; do not buy again merely to troubleshoot.

License Management provides deactivation for releasing this installation’s activation. It does not delete conversations or issue a refund. Deactivation needs a successful service response.

Local storage and network activity

Local chat processing does not mean that the application never communicates. The following behavior is present in the reviewed implementation.

When communication can occur
OperationBehavior
Chat reading and searchStored conversations are processed on the Mac; no chat-upload endpoint was found in the reviewed paths.
iCloud importmacOS may download the LINE backup from iCloud. Apple Account and iCloud activity are handled by Apple’s services.
License serviceActivation sends the license key and Mac computer name to Lemon Squeezy. Validation/deactivation sends the key and activation instance identifier.
2.0 sticker loadingRequests to LINE’s CDN identify the sticker; the server also receives ordinary connection information such as the IP address.
Links and saved filesOpening websites, buying the app or saving into synchronized folders can involve other services.

An activated installation may validate its license at startup after 7 days since activation or the last successful validation. A network failure preserves the previous activation state in the reviewed implementation; an invalid-license response can disable paid exports. Do not interpret that behavior as a promise of permanent offline activation.

License credentials are held in macOS Keychain. The conversation database is a separate local file. Already imported text can be read without fetching the source again, but first-time iCloud downloads, activation and uncached 2.0 stickers can need connectivity.

Back up and remove data

Before another import or moving Macs

  1. Quit ChatArchive completely.
  2. In Finder, use Go → Go to Folder and enter ~/Library/Application Support/ChatArchive/.
  3. Copy the entire folder to a dated, protected backup location. Include any database companion files and sticker cache.
  4. Keep important reading exports and the original source backup separately. Check that your backup copy exists before proceeding.

This preserves the local files; the reviewed UI has no supported database-restore wizard or library merge. For migration or recovery, keep the original copy untouched and ask support about version compatibility. License activation may also need to be performed separately on another Mac.

Remove local history

There is no per-chat deletion command in the reviewed interface. After quitting and making any required backup, you can move the ChatArchive Application Support folder to Trash in Finder. This removes the local working library when the files are actually deleted; a later launch creates a new empty library. Remove exports and backup copies separately if desired.

Deleting the app alone does not necessarily delete its Application Support files or Keychain license. Removing ChatArchive files does not remove the original LINE conversations or iCloud backup. Trash, system backups and cloud copies have their own retention behavior; this is not a secure-erasure function.

Troubleshooting and useful support reports

Symptoms and checks
SymptomCheck
Mac data not foundConfirm LINE for Mac has been installed and used with the intended account. The current LINE storage format may differ from the supported one.
Permission/key/decryption errorKeep LINE running and signed in. Check Developer Tools permission. If it still fails, report the exact error and versions.
iCloud backup not foundCheck a completed LINE iPhone backup, the Mac’s Apple Account and iCloud Drive availability. A generic device backup is not sufficient.
Archive extraction failsAllow the iCloud file to download completely and check free space. Backup format differences, including missing supplementary files in 2.0, can also cause failure.
Old messages seem missingLoad older pages; inspect source coverage and the selected backup. Repeated import cannot recover absent history.
Dates look wrongPreserve the source and contact support. The 1.0.0 source uses an older iCloud timestamp conversion.
Search finds nothingPress Return, change terms and remember the 100-result limit and word/prefix matching. Chat-name filtering is a separate field.
Export stays lockedCheck activation and compatible key delivery. For free 2.0 HTML, select a chat and explicitly choose Selected Chat.
Text import or HTML is absentMarketing text may describe another version. The reviewed 1.0.0/2.0 main interface has no text-file import command; HTML/Markdown are 2.0-only.

Contact hakaruapps-contact@hakaru.net with the ChatArchive version/build, macOS version, LINE version where relevant, import route, exact error and short reproduction steps. Include whether the problem occurs before or after an import completes.

Start with a description rather than sending a conversation database, backup ZIP, license key or private screenshots. If examples are needed, remove names, conversation text, paths containing personal details and credentials. This manual was produced by reviewing distribution metadata and source code; it is not a live-import compatibility test against every current LINE version.