LibSync (Library Synchronizer) was designed with AutoCAD libraries in mind, but works for any folder — from project archives to a simple backup of your documents. Only what's new, changed or deleted goes across, with an automatic backup before every change and a safe orphan workflow.
No more full copy-paste rounds. LibSync detects per file whether it's new, changed or deleted.
Edit your tool palettes locally, stage them to your library, sync them to the server in one go.
Files left behind on the target side are shown separately — nothing is silently deleted.
Before LibSync overwrites or deletes a single file, it automatically creates a backup — kept separate per sync run. Something went wrong? Restore it through an explicit flow with a mandatory preview, never automatically.
Compares source and target per file on time, size and content.
Multiple source/target configurations side by side for library, palettes and projects.
From AppData to your local library, then to the network share.
Orphan files are shown separately with an explicit choice.
No deletions without confirmation by default.
Efficient over slow or busy company shares.
Calm interface, even on long sync sessions.
English interface plus seven other languages.
Work in your tool palettes or library on your own workstation.
From AppData to your central library folder — controlled.
LibSync determines exactly which files are new, changed or orphan.
Confirm and the network share is up to date — no unnecessary transfer.
LibSync is built for managing a company CAD library, but the engine is generic — any folder pair that must stay consistent fits.
Blocks, tool palettes, templates and support files to the company share.
Move completed projects periodically to an archive drive.
Any tool with a local and central folder — Revit families, Inventor content, standards.
Any folder that needs a regular copy — documents, project folders, photos — benefits from the same safe sync-and-backup engine.
Blocks, templates, tool palettes, standards and LISP routines live on a network share in most firms, but get edited locally. Without discipline you end up within months with a collection of versions and nobody knows which one leads. LibSync fixes that with an explicit, reviewable synchronisation instead of manual copy-and-paste.
A full copy pass over a library of thousands of files costs time and rewrites timestamps on files that never changed. LibSync compares source and target per file and presents the result in four categories: new, changed, unchanged and orphan. Before synchronising you see exactly what will happen, including file count and total transfer size.
AutoCAD stores tool palettes in your user profile under AppData — a folder that is rarely part of a backup or sync routine. LibSync stages those palettes into your library folder and carries them to the server in the same pass, so a palette one drafter improved does not stay stuck on a single workstation.
Files that only exist on the target side are included in the normal sync deletions by default, after the usual confirm-with-counts step. Want to review them separately first? Turn off 'Synchronise deletions': LibSync then lists every orphan with its path and size, and you pick one action — skip, delete, copy back to source, or rename — applied to the whole list.
Most firms sync the same paths over and over: library to server, standards to a project folder, palettes to a department share. Save those routes as profiles so a sync round becomes pick, scan, review, run. Not every folder has to come along either: filters keep temporary files and backup folders out of the comparison.
No. LibSync synchronises any folder to any other folder. The AutoCAD-specific features — such as staging tool palettes out of AppData — sit on top of a general folder sync.
No — that's the core design principle. Before LibSync overwrites or deletes a file, it automatically backs that file up. That backup can always be restored.
Every sync run gets its own timestamped backup, with changed and deleted files kept separately. Restore lets you pick an earlier run, review a mandatory preview of what will be restored, and only then confirm — never automatically.
Yes — with 'Synchronise deletions' on (the default), files no longer in the source are removed automatically, after a confirm step showing counts. Turn that setting off and they're shown as orphans instead, with path and size, so you choose what happens to them.
Yes. Source and target can be a local folder, a mapped network drive or a UNC path, as long as your Windows account has rights on it.
Yes. The scan lists the status per file plus a summary with count and size. Nothing is written until you confirm.
No. LibSync runs as a standalone Windows application on the workstation and uses only the network rights you already have.
The application is finished and tested; sales start once the payment environment is live and the business registration is complete.
LibSync is feature-complete and tested. Sales will start as soon as the payment environment leaves sandbox and business registration is complete.
