WHAT TO DO WHEN ENDNOTE MAC AND WINDOWS LIBRARIES DON'T SYNC
2026 Troubleshooting Guide

EndNote's cross-platform guide says syncing creates a library copy on the target computer, and record numbers may change. That means a changed record number alone does not prove a reference was lost.

Symptom → fastest safe action: If the libraries differ, first identify the copy with the latest references, groups, and attachments; make a recoverable backup before another sync.

Do not repeatedly sync two populated libraries to “fix” a mismatch. For ongoing Mac–Windows work, use the supported sync process with one chosen account. For a one-time handoff, back up and transfer a compressed library copy, then verify attachments and paper citations on the receiving computer.

Who this is for: Graduate students moving between Mac and Windows while writing a thesis or paper. Lab reference managers who need a safe backup, handoff, and acceptance process. Researchers without a local Mac who need to know when they must check their workflow in macOS.

Identify which library is safe to work from

Before troubleshooting, stop editing both copies. Write down where each library is stored, when it was last changed, and the last time sync completed without an error. Compare recent references, group names, and a few attachment links. The library with the newest timestamp is not automatically the best source: a recent change may be incomplete, or its PDFs may point to files unavailable on the other computer.

EndNote libraries involve more than the visible .enl file. The related .Data folder can contain the library’s associated files, including attachments. EndNote’s backup guidance explains which library components to preserve. Keep the .enl file and its matching .Data folder together when making a local copy or preparing a transfer.

Create a backup that you can restore before trying to merge, resync, repair attachment paths, or upgrade a library. Preserve the original copies as they are; do not rename or delete components to make the folder look tidier. Record the EndNote version on each computer and the exact location of each library. Those notes help you tell a version issue from a file-location or sync issue.

A useful initial comparison is small and deliberate. Choose references added or edited recently, a reference with a PDF, and a group whose membership matters to your project. Confirm that you can open the attachment, not just see its filename in EndNote. If one copy has unique groups or annotations, preserve it even if the other copy appears to have more references.

Restore sync without creating another set of duplicates

For continuous work across computers, use EndNote’s account-based sync workflow rather than treating a cloud folder as a substitute. EndNote’s cross-platform instructions describe transferring libraries between platforms and creating a target-side library copy. Follow the current instructions for the EndNote versions installed on both machines.

Duplicates often arise when an existing library is used to initialize sync against a destination that already contains some of the same references. EndNote’s library merge and sync guidance warns about this condition. Before attempting any merge, retain an untouched copy of each library. Then compare actual reference details—such as title, author, year, and attached files—rather than relying only on record numbers.

Use this recovery sequence:

1. Pause edits and sync activity. Close the library on the computer where the problem appeared. Avoid making new changes on both machines until you know which copy you will use as the recovery source.
2. Make separate backups. Copy each library and its matching .Data folder to a location that is not being actively synchronized. Keep the copies identifiable by computer and date in the folder name.
3. Choose an authoritative library. Compare recent references, group membership, notes, and attachments. If each copy has unique work, do not simply declare one the winner; preserve both and prepare to reconcile them in a working copy.
4. Check the sync state and account. Confirm the account and the library you intend to sync. Review the latest successful sync status available in EndNote. If the status is unclear, do not start a fresh initialization with two populated libraries.
5. Follow the documented sync or merge path. Use the official steps that match your situation and software version. Do not improvise by repeatedly signing out, deleting local folders, or replacing the .enl file.
6. Verify the receiving library. Check the representative references and groups you recorded earlier. Open PDFs from the receiving computer, not just from the source machine.
7. Test a paper before resuming normal work. Open a copy of the relevant document, update citations if needed, and compare the in-text citations and bibliography with the expected output. Keep the untouched backups until the test passes.

If a sync is still incomplete, treat that as a sync-state problem, not proof that references need to be merged. Recheck the selected library and account, then retry only after the backups are confirmed and the current official instructions match your setup. Account status, network access, and a particular library’s state can each affect an individual case; the documentation cannot establish that every user's account or file is healthy.

Separate missing PDFs from missing references

When a citation appears in EndNote but its PDF will not open, first establish whether the reference record arrived. Then inspect the attachment itself. EndNote distinguishes files stored with the library from links to files elsewhere. Its relative and absolute attachment path explanation describes why a path that works on one computer may not resolve on another.

A PDF linked by an absolute path can still point to a location that exists only on the original computer. In that case, syncing the reference does not make the file available at the destination path. Files in the library-associated .Data folder may transfer with the library package, but you must confirm that the relevant file is present and usable on the target. EndNote’s instructions for finding broken attachment links can help identify links that no longer resolve.

Use a sample rather than assuming every attachment has the same problem. Select a few references with different attachment histories: a recently added PDF, a file stored with the library, and one that may have been linked from a local folder. Open each on the destination computer. If only linked files fail, repair or relocate those links in a working copy, then test them again. If files stored with the library are also missing, return to the backup and transfer checks before editing individual references.

Keep the source PDF files until the destination copy has been tested. Moving or deleting a source folder while EndNote still points to it can turn a temporary handoff issue into broken links in the working library.

Keep active libraries out of file-sync folders

Do not open an uncompressed active EndNote library directly inside a folder that another file-sync service is still processing. A library is a group of related files, not just a single .enl document. If the main file and its associated data do not move or update together, you can see an incomplete library or unexpected changes.

EndNote’s cross-platform documentation discusses cloud-folder risks and recommends using a compressed library for transfer rather than working from an uncompressed active library in common cloud-sync locations. A compressed library is a handoff copy; it is not a reason to delete the source library before you have verified the destination.

For a controlled transfer, use this order:

• Close the library before preparing the transfer copy.
• Use EndNote’s compressed-library workflow, following the instructions for your installed version.
• Move the resulting package to the recipient through an agreed, access-controlled method.
• Open it on the destination computer and check references, groups, and representative PDFs.
• Keep the original until the recipient confirms that the test passed.

For shared lab access, decide whether the need is collaboration or simply distribution of a copy. EndNote’s [network-use guidance](https://docs.endnote.com/docs/endnote/2025/v1/macos/en/content/25networks/endnote_on_networks.htm) covers network and multi-user access considerations. Do not assume that placing one active library on a shared drive makes simultaneous editing safe; confirm that your intended arrangement matches the documented method and your institution’s storage rules.

Check versions and citations before declaring data loss

A library can appear inconsistent even when its references are present. Check the EndNote version on each computer and whether the library format is supported by the version that is opening it. If a library was converted or updated, keep the pre-conversion backup. Do not use a one-way conversion as a repair experiment on the only copy.

Also distinguish a library mismatch from a Word citation mismatch. A paper may contain citation fields from a different writing session or library state. Check a copy of the document first, then use EndNote’s documented Word citation commands to update and inspect citations. Compare the bibliography and in-text references with the intended library; do not infer that a missing-looking item is gone just because a record number changed.

If you are handing a project to a lab mate, include the library package and a short note describing the EndNote version, the source computer, the transfer date, and which paper copy you tested. Do not include account credentials. The recipient should open a working copy, check a representative attachment, and review citations in a document copy before replacing their existing library.

Choose the workflow by use case

The right method depends on whether you are continuing your own work across computers, handing a snapshot to someone else, or supporting shared access. These options are not interchangeable.

<

Use case	Preferred route	Main risk to control	Acceptance check
You move between your own Mac and Windows computers	EndNote’s documented account-based sync process	Initializing sync with two populated libraries or the wrong account	Confirm references, groups, attachments, and a test paper on both computers
You are sending a library to a colleague	Back up, then send a compressed library copy	Sending only the .enl file or assuming linked PDFs are included	Recipient opens the copy and checks representative PDFs and citations
A lab needs shared access	Confirm the intended setup against EndNote’s network guidance and local policy	Assuming a shared folder allows safe simultaneous editing	Test permissions, access, and the actual collaboration workflow before use
You need to inspect an issue without changing the official library	Work from a separate backup copy	Accidental edits or sync changes reaching the only usable library	Compare the test copy with the preserved original before adopting changes

Before returning to the main library, use this acceptance list:

• [ ] Identify the copy that contains the newest required references, groups, and notes.
• [ ] Preserve both source libraries and their matching .Data folders before making changes.
• [ ] Record the EndNote version and the account or transfer method used.
• [ ] Confirm the receiving copy opens without an error.
• [ ] Open representative PDFs on the receiving computer.
• [ ] Check group membership and recently edited references.
• [ ] Update citations in a paper copy and inspect the reference list.
• [ ] Keep the backups until the receiving researcher confirms the handoff.

FAQ: common Mac and Windows library problems

How do you keep one EndNote library synchronized on Mac and Windows?

Choose the authoritative library, create a recoverable backup, and follow EndNote’s documented sync process for the same account. Avoid copying an active, uncompressed library between cloud-synced folders as a substitute. On the receiving computer, check references, groups, attachments, and a test paper before returning to normal work. If both libraries contain unique changes, preserve both and use the documented merge guidance on working copies.

Why can syncing create duplicate references?

Duplicates can appear if you initialize sync with an existing library while the destination already contains some of the same references. Stop repeating the sync, preserve separate copies, and compare reference details and group membership before removing records. EndNote’s merge guidance explains the initialization issue. Record numbers can change during cross-platform work, so use the reference content and attachments—not the number alone—to determine what is present.

What should you do when reference records arrive but PDF attachments do not?

Check whether each PDF is stored in the library’s associated .Data folder or linked by a path to a file elsewhere. A linked file may remain on the source computer even when its reference record syncs. Test representative attachments on the destination machine. If a path is broken, repair it in a working copy and retest before changing or removing files from the source location.

Is it safe to keep an active EndNote library in OneDrive or iCloud?

Avoid opening an uncompressed active library directly from a folder that a cloud-sync service is processing. EndNote’s guidance distinguishes an active library from a compressed transfer copy and describes risks with common cloud-synced locations. For continuing work across your own computers, use the documented sync workflow. For a one-time handoff, transfer a compressed copy and confirm that its references and attachments open on the receiving computer.

If the problem appears only on the Mac, first test the desktop workflow in a separate, recoverable copy and use the checks above to identify whether the issue is sync state, file paths, or citation fields. When you have no local Mac but need to verify a macOS desktop workflow, review MACGPU’s remote Mac options and decide whether temporary access fits the task; a local machine may be a better choice for sustained daily work or tasks that require physical connections. If you proceed with a remote environment, use a non-sensitive test copy first, then confirm the transfer and citation checks before moving your research library. You can review the available Mac access options if you need a Mac environment for that verification.