Files and locations

Where Rhino Sync keeps settings, local copies, sign-in data, logs and program files.

Windows

What	Location
Settings	%AppData%\Rhino.Sync\settings.json
Local copies	%LocalAppData%\Rhino.Sync\Cache\
Cloud storage sign-in	%LocalAppData%\Rhino.Sync\google.link, microsoft.link and dropbox.link, encrypted for your Windows account
Debug log	%LocalAppData%\Rhino.Sync\Logs\debug_log.log
Program files (installer)	C:\ProgramData\Rhino.Sync\App\netcore\

macOS

What	Location
Settings	~/Library/Application Support/Rhino.Sync/settings.json
Local copies	~/Library/Caches/Rhino.Sync/
Cloud storage sign-in	macOS Keychain, service Rhino.Sync, one item each for google, microsoft and dropbox
Program files	Rhino Package Manager packages folder

Local copies

When you collaborate, Rhino Sync copies the central file into the local copies folder and opens it. The copy is named after the central file, a random ID and your user name, such as Riverside Tower_3f2a…_Hana.3dm.

Rhino Sync deletes your local copy when you end collaboration. A central file downloaded from Google Drive, OneDrive or Dropbox stays in a subfolder named after the file ID.

Don't open or edit files in the local copies folder yourself. Use Collaborate.

Debug log

On Windows, Rhino Sync always writes technical messages to debug_log.log. When the file passes 5 MB, it's renamed with a date and a new one starts. The 3 newest old logs are kept.

Send this file with your support request.

Next to a network central file

Rhino Sync creates a _collab folder next to a central file on a network drive. See Network Drive.