The details we like to know up front.

Start from the project you want to run, with its textures, models and final settings. Measure the requirement on a representative test when possible, then keep some headroom for the heaviest steps. A 48 GB card makes sense if 24 GB limits your scene or your graph; memory capacity alone determines neither compatibility nor software speed.

Start by checking the GPU engine supported by your version of Blender. RTX cards are candidates to consider for a Cycles workflow using CUDA or OptiX. The weight of the scene, textures and geometry then guides the memory choice. Do a control render with the full scene before launching an animation.

Keep the workflow JSON, the required models and their location, the versions of the custom nodes and a test image. An exported graph does not contain all the weights or all the dependencies. Check the rights for each asset and test the complete workflow, including the output and the finishing steps.

Not automatically. The software must explicitly distribute the data or the processing across the GPUs. A batch of two B200s provides two cards with their respective memory; it does not guarantee that a program will see a single doubled memory space. For an animation, distributing independent frames can be another approach, depending on your tools.

Yes. Each B200 batch includes two cards, each with 180 GB of memory. The price shown covers the complete batch. Recheck the number of batches in the configurator: two batches therefore correspond to four GPUs.

Choose three days for a targeted step whose assets are ready, seven days for a series of tests and corrections, or thirty days for a project you follow over time. Include the time for preparation, checking and retrieving results. These durations structure the rental; they do not promise a number of renders.

The catalog shows the price of the full lot for the selected duration. The listing indicates the number of cards included. The configurator multiplies this price by the number of lots requested and displays the total number of GPUs. Orders are expressed in USD.

No. RenderParcel offers crypto payment with no KYC procedure and no ID. Your email, first name and last name are stored in your account and used as order contact details. You create this account with a password, or you log in before ordering. The email address is not verified by sending an email.

After your transfer, you can report it in the order with "I've paid", choosing the instructions that match your transfer. The payment status depends on the confirmation received from the server. This button records your report; it does not confirm payment, does not credit the balance and does not start a GPU.

A rental corresponds to a GPU configuration and a duration. A top-up adds credits that can be used to pay for rentals, once only after the server confirms its payment. Creating a top-up or reporting its transfer is not enough to increase the balance. Each transaction can be found in your studio's tracking.

Keep the order reference and the details visible in your wallet, then submit a request from the studio. Never share a private key or recovery phrase. Do not automatically send funds back: the payment status and any discrepancies must first be reviewed.

Yes, you choose the software and processing for your project. Check their compatibility with the GPU, system and dependencies you prepare. Licenses for software, extensions, weights and assets must be suitable for your use; no additional commercial license is stated as included.

The service does not inspect the content of your files, prompts or computations. This does not remove the data required for the order and payment. Keep only the useful information in your notes and protect access to the browser you use.

Check its status in the studio. Registration, payment and preparation each have their own tracking. An order awaiting payment or preparation is not an active GPU session. Tracking lets you distinguish these steps without confusing a payment report with its confirmation.

Export the results from your tools, then keep the sources, versions and decisive parameters with an independent copy. The studio notebook gathers your notes and can be downloaded as JSON; it does not replace a backup of your creative files. Check a few exported files before closing your work session.

Log in with the email and password of your RenderParcel account. You get back its orders, balance and notebooks, including from another browser. Clearing the cookie or letting the session expire requires logging in again, without deleting the account data. If you have forgotten your password, email-based reset is not available.

The Documents section offers summaries of your orders. They let you keep the associated configuration, contact details and tracking. These exports are not tax invoices or standalone proof of transfer. Log in to your account to find them and keep a copy of the useful documents.