Found a bug? Meow it! 🔗

Consider consulting our Add-on troubleshooting guide; it is often the fastest way to get your problem fixed. Before reporting a bug, please also check existing GitHub issues; often you can find the fix or workaround there. If your bug is still unresolved, please report on our GitHub page.

For payment or website difficulties, please email us for assistance at [email protected].

Report add-on Bug on GitHub Contact Us

How to Get BlenderKit Error Logs 🔗

To effectively help you resolve issues, we we need something called log files - that's where the add-on writes down any error messages. Please send us your complete Blender logs if you report the bug on GitHub, or in email.

Depending on your operation system, here is how you get the Error Logs for BlenderKit add-on and its background BlenderKit-Client:

Getting BlenderKit Error Logs on Windows

  1. Locate Blender.exe and Client's log file:
    1. Client log is by default at: C:\Users\<your-username>\blenderkit_data\client\default.log.
    2. Blender.exe is by default located at: C:\Program Files\Blender Foundation\Blender 4.1\blender.exe. Please change the 4.1 in the path to the version of Blender you are using, e.g.: 3.6, 4.0, 4.2.
  2. Click on the Start button and search for PowerShell. Launch the PowerShell application twice.
  3. In first PowerShell window, type (or paste by right-clicking) the following command: Get-Content C:\Users\<your-username>\blenderkit_data\client\default.log -Wait (use path from step 1.a), hit Enter to execute the command. PowerShell will now monitor the BlenderKit Client's log file. We will use it later. Make sure the path to Client log is correct.
  4. In second PowerShell window, type (or paste by right-clicking) the following command into the PowerShell window: & "C:\Program Files\Blender Foundation\Blender 4.1\blender.exe" (make sure the path - from step 1.b is enclosed in quotes). Press "Enter" to run the command, which will start Blender. All errors which happen during the run will be printed into the PowerShell window.
  5. Use Blender as usual until you encounter the problem. Then, copy and paste the full text from both PowerShell windows into your Github issue, or into your email. To select text, hold down the left mouse button and then copy it by pressing the right mouse button.

Getting BlenderKit Error Logs on MacOS

  1. Locate the Blender binary and the Client's log file:
    1. The Client log file is typically located at: /Users/<your-username>/blenderkit_data/client/default.log.
    2. The Blender binary is by default found at: /Applications/Blender.app/Contents/MacOS/Blender.
  2. Open Spotlight and search for Terminal. Launch two instances of the Terminal application.
  3. In the first Terminal window, type tail -f command followed by path from step 1.a, e.g. tail -f /Users/<your-username>/blenderkit_data/client/default.log and press "Enter". Terminal now begins monitoring the log file.
  4. In the second Terminal window, type or paste the path from step 1b, e.g., /Applications/Blender.app/Contents/MacOS/Blender, and press "Enter". This will start Blender, and any errors will be displayed in the Terminal window.
  5. Use Blender as you normally would until the problem occurs. Then, copy and paste the full text from both Terminal windows into your Github issue, or into your email.

Getting BlenderKit Error Logs on Linux

  1. Locate the Blender binary and the Client's log file:
    1. The Client log file is typically located at: /home/<your-username>/blenderkit_data/client/default.log.
    2. The Blender binary can be located by typing which blender in the terminal. If the blender binary is not on the PATH, search for its location and use the absolute path for the following steps.
  2. Launch two instances of the Terminal application.
  3. In the first Terminal window, type or paste the following command: tail -f /home/<your-username>/blenderkit_data/client/default.log (use path from step 1.a) and hit "Enter". Terminal now begins monitoring Client's log file.
  4. In the second Terminal window, type blender (or specify the absolute path from step 1.b) and hit "Enter". This will start Blender and any errors will be printed into the Terminal window.
  5. Use Blender as you normally would until the problem occurs. Then, copy and paste the full text from both Terminal windows into your Github issue, or into your email.