# Upload projects using Botaniq Addon **Tree library Botaniq addon** is an ever-expanding library of optimized & realistic 3D vegetation - mostly trees and grass. This article will show you how to **upload projects using Botaniq addon** to 3S Cloud Render Farm. Remember that after this the scene will be much bigger as everything is in it even the geometry. You might want to save the new .blend as \_PACKED.blend and send that to our render farm while reverting to the non-packed version later. When you use Make Local, all the linked geometry+material collections are made Local. So your file size inflates, let's say from 230 MB to 800 MB depending on how many different assets you had in the scene. 1. Select all linked collections (all botaniq assets) and make them Local by going into Objects > Relations > Make Local > All
Upload projects using Botaniq Addon
Then you [Pack All into .blend](https://3sfarm.com/support/how-to-use/tips-for-blender/how-to-pack-a-blender-file-before-uploading/) as usual. After that, you can upload projects using Botaniq Addon to our render farm! See more instruction for [**Botaniq - Blender 3.0**](https://blendermarket.com/products/botaniq-trees/faq) Don’t hesitate to [contact us](https://3sfarm.com/contact/) with any issues. We are pleased to assist you. [3S Cloud Render Farm](https://3sfarm.com/) currently supports [Blender](https://3sfarm.com/blender-render-farm/), [Houdini](https://3sfarm.com/houdini-render-farm/), [Cinema 4D](https://3sfarm.com/cinema-4d-render-farm/), [Maya](https://3sfarm.com/autodesk-maya-render-farm/), [3ds Max](https://3sfarm.com/3dsmax-render-farm/). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.3scloud.io/3s-cloud-render-farm/tips/tips-for-blender/upload-projects-using-botaniq-addon.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.