Symptoms
Identical bookmark folders multiply following iCloud sync between two previously separate Macs.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Identical bookmark folders multiply following iCloud sync between two previously separate Macs.
- Comparison to run: Compare folder contents and sync times without deleting any bookmark.
- Pass condition: A single shared test folder remains stable across both Macs.
Why It Happens
Account permissions and synchronization queues need independent checks: the server copy can be correct while a particular desktop or mobile profile is stale.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Two local bookmark trees merged — investigate this first only if the local state or controlled comparison supports it.
- Sync conflict replayed stale copy — a second layer that may survive a simple restart and requires a targeted check.
- Third-party browser import added duplicates — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Never mass-delete bookmarks until an export and a restore test exist. Several accounts or profiles can display the same name while storing separate content and permissions. Identify the exact signed-in identity and the owning account before changing a shared resource. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare folder contents and sync times without deleting any bookmark. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare folder contents and sync times without deleting any bookmark. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Export bookmarks on both Macs before any cleanup. | This can expose or rule out two local bookmark trees merged without changing several settings together. |
| Inspect the deeper layer | Check which devices or browser-import jobs are still creating copies. | Use the evidence to separate sync conflict replayed stale copy from third-party browser import added duplicates; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether sync conflict replayed stale copy is consistent with the evidence. If not, investigate third-party browser import added duplicates rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Identical bookmark folders multiply following iCloud sync between two previously separate Macs. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare folder contents and sync times without deleting any bookmark. Do not erase logs or reset the device yet. Export bookmarks on both Macs before any cleanup. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Compare the folder trees in Safari's bookmark editor. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. A single shared test folder remains stable across both Macs. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider two local bookmark trees merged, sync conflict replayed stale copy and third-party browser import added duplicates separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare folder contents and sync times without deleting any bookmark. Check which devices or browser-import jobs are still creating copies. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Deduplicate one test folder and verify changes propagate before further deletion. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. A single shared test folder remains stable across both Macs. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating two local bookmark trees merged as certain before running the comparison: Compare folder contents and sync times without deleting any bookmark.
- Trying several changes at once, such as modifying sync conflict replayed stale copy and third-party browser import added duplicates simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Never mass-delete bookmarks until an export and a restore test exist.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
A single shared test folder remains stable across both Macs.
- Repeat the original failing action under equivalent conditions: Identical bookmark folders multiply following iCloud sync between two previously separate Macs.
- Run the control again: Compare folder contents and sync times without deleting any bookmark.
- Check the positive pass condition: A single shared test folder remains stable across both Macs.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Check which devices or browser-import jobs are still creating copies. Deduplicate one test folder and verify changes propagate before further deletion.
Tell the service owner the affected account alias, item type, client type and timestamps, but never send passwords, recovery codes, full tokens or private shared documents.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare folder contents and sync times without deleting any bookmark.
- Preserve the corrected behavior: A single shared test folder remains stable across both Macs.
- Keep a current backup or export of irreplaceable local records and review sharing permissions when changing devices or accounts.
- Review configuration or hardware changes that could reintroduce two local bookmark trees merged.
Frequently Asked Questions
Does this symptom prove two local bookmark trees merged?
No. Start with the controlled comparison: Compare folder contents and sync times without deleting any bookmark. Only treat two local bookmark trees merged as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Check which devices or browser-import jobs are still creating copies. That helps determine whether sync conflict replayed stale copy or third-party browser import added duplicates fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: A single shared test folder remains stable across both Macs. Keep a record of the working state for future troubleshooting.