A beginner’s guide to Xesktop
What is Xesktop?
Xesktop is a server rental service that gives users access to remote GPU servers that behave like cloud-based Windows computers. Instead of buying or upgrading a powerful workstation, you can rent GPU power when you need it and control the server through a Remote Desktop connection.

For beginners, the easiest way to understand Xesktop is this: your own computer is used to connect, while the heavy work happens on a stronger machine in the cloud. This can help when your local machine struggles with rendering, AI generation, simulations, high-resolution scenes, or GPU-heavy software.
A service connected to GarageFarm.NET
Xesktop exists alongside GarageFarm.NET’s cloud rendering service. If you already have a GarageFarm.NET account, you may be able to use the same login details for Xesktop. The difference is in the workflow. GarageFarm.NET is focused on render farm submission, while Xesktop gives you direct access to a remote GPU workstation.
Who is Xesktop for?

Xesktop is built for people who need more GPU power without buying a new machine. This can include freelancers, studios, AI users, 3D artists, designers, developers, and production teams. It is especially useful when a task needs a strong GPU for a limited amount of time. Instead of investing in expensive local hardware, you can rent a server for the session, project, test, or production period.
3D artists and render users

For 3D artists, Xesktop can be used to run GPU render engines and creative applications. This may include workflows in Blender, Cinema 4D, Maya, 3ds Max, Daz 3D, OctaneRender, Redshift, Cycles, and other GPU-based tools. It can help when a scene is too heavy for a local workstation, when deadlines are tight, or when you want to keep your own computer free while rendering happens remotely.
AI and ComfyUI users

Xesktop can also support AI workflows, including ComfyUI on supported machines. This is useful for image generation, video generation, model testing, AI development, and other workflows that need more VRAM. For users who do not have a high-end GPU locally, Xesktop can make heavier AI workflows more accessible.
Studios and production teams

Studios can use Xesktop when production demand temporarily grows. A team may only need extra GPU power during a deadline, testing period, or heavy render stage, so renting a remote workstation can be more practical than buying new hardware. Because each system runs as its own remote desktop, teams can also keep workflows separated while still using shared storage for project data.
How the Xesktop dashboard works

After logging in, the Xesktop dashboard is where you manage your servers, images, credits, and connection details. This is the main control center for starting and stopping your remote workstation. The dashboard also shows useful details such as server availability, credit balance, image activity, lease duration, and cost.
Comparing available servers and other information

From the dashboard, you can browse the available server options by going to the info panel, and clicking “compare” beside the Server specs. You can also use the comparison view to see different servers side by side. This is helpful because different jobs need different types of GPU power. A render job, AI workflow, or GPU-dependent tool may benefit from a server with more VRAM, more GPUs, or a newer GPU model.
You can also find various resources in this info panel. To close the whole thing, simply click the blue text “hide info panel”. To reopen it, click the blue text “show info panel” located below the navigation bar.
Checking credits and availability

The top area (or navigation bar) of the dashboard shows account details such as credits and server availability. Before starting a long session, check that you have enough credits for the work you plan to do.This is especially important before running long renders, AI batches, or production tasks that may continue for several hours.
Checking image activity and creating new images

The area below is where you can find your image activity. On the right side, you may filter the images via All, Active, Inactive, and Preparing. On the left, you can click the “new image” button to create a new image.
How to get started with Xesktop
The first setup takes a little time because Xesktop needs to create your system image and boot the server. Once that is done, connecting becomes much easier.
Step 1: Create a new image

To begin, click the option to create a new image. You will be asked to add a description or name for the image. This name is mainly for your own organization, so choose something related to the project, tool, or workflow.
Clicking YES to “Boot system right after the image is ready?” pertains to automatically starting the machine as soon as the new image has finished being created.
Step 2: Wait for the image to be created

After you create the image, Xesktop prepares a fresh Windows environment. This can take several minutes, so it is normal if the image is not ready immediately. Once the image is ready, you can go to its card and see its current state, activity, lease duration, and cost from the dashboard.
Step 3: Set the resolution

Before booting the system, you may be able to choose the display resolution for the remote desktop by clicking the three dots beside the trash icon, and go to Set RDP resolution. This helps match the server view to your monitor or preferred working setup. A higher resolution can make the workspace more comfortable, especially for 3D, compositing, or node-based tools, but it may also depend on your local display and connection quality.
Step 4: Boot the system

When the image is ready, click the button with the play icon. Xesktop may show a list of available GPU servers that you can choose from. Pick the server that fits your task. A heavier render, AI model, or GPU-intensive application may need a stronger GPU, while lighter setup work may not require the highest-end option.
Step 5: Download the RDP file

After the system is running, download the RDP file from the dashboard. This file contains the connection details needed to access your remote desktop. You can open it with a Remote Desktop application. On Windows, this may open directly. On macOS, you can use a Remote Desktop app such as the Windows App or Microsoft Remote Desktop.
Step 6: Log in to the remote desktop
When connecting through RDP, use your Xesktop account details. The username may be your account number, which can be found in the dashboard, and the password is the same one used for your Xesktop account. After logging in, you will enter the remote Windows desktop. From there, you can begin setting up the system and working on the server.
Installing software on Xesktop
Once connected, you can install the applications you need for your workflow. This may include 3D software, render engines, AI tools, plugins, utilities, browsers, file transfer tools, and monitoring software. The important thing is to install applications in the right place and keep project files separate from system files.
Use the C drive for applications

The C drive is the system drive. It is the right place to install applications, plugins, and program files because it is designed for the operating system and installed software. You should avoid using the C drive or desktop as your main project storage location. Treat it as the place for software, not as the place for working files or final outputs.
Use the user drive for working files

Your working files should go on the user drive or shared storage drive, often shown as the U drive. This is where you should save project files, source assets, render outputs, AI results, caches, and other important data. This drive is also useful because it can be accessed through FTP. That means you can move files in and out more safely without relying only on the live remote desktop session.
Keep your setup reusable
Applications installed on the system image are preserved, so you do not need to reinstall everything every time you boot the same image. This is one of the biggest advantages of using a saved image. After your software is installed and configured, you can reuse the image for future sessions and continue from a familiar workspace.
Moving files in and out of Xesktop
File transfer is an important part of the workflow. You need a reliable way to bring project files into the remote workstation and download final outputs when the work is done. There are several ways to do this, depending on your workflow and file size:
FTP access
FTP is one of the main ways to access files stored on the user drive. This is useful because your files can be reached even when the server is not actively being used. For large projects, FTP can be more organized than dragging files through a remote desktop session. It also helps keep files in the correct storage location.
Cloud storage

You can also use cloud storage services such as Google Drive or Dropbox to transfer files, depending on your setup. This can be convenient if your project files are already stored in the cloud. However, cloud services may need extra configuration, especially when syncing to a remote machine or working with large files. For production work, always confirm that files have fully uploaded or downloaded before starting.
Remote Desktop copy methods
For smaller files, you may be able to copy and paste or move files through the Remote Desktop session. This can be convenient for quick transfers, but it may not be the best choice for large projects or heavy render outputs. For serious work, FTP or organized cloud transfer is usually easier to manage.
Billing and credits

Xesktop uses a credit-based, pay-as-you-go model. The exact cost depends on the server type and current pricing, so you should always check the dashboard before starting a long session. The main thing beginners need to remember is that credits are used while the server is running.
Billing starts when the server is running
Once a server is booted and active, billing begins. Usage may be calculated in small time increments, so even shorter sessions can be billed fairly. This gives you flexibility, but it also means you should be careful not to leave the server running when you are no longer using it.
Billing stops when the server is shut down
Closing the Remote Desktop window does not necessarily stop the server. It may only disconnect you from the session. To stop charges, shut down the server properly from Windows or through the Xesktop dashboard. Make this a habit at the end of every session.
Add credits before long jobs
If you are planning a long render, AI batch, or heavy processing session, check your credits before starting. Running out of credits during a job can interrupt your workflow. It is better to estimate the cost first, add credits if needed, and then start the job when you are ready.
Software licenses
Xesktop provides the remote server, but it does not automatically provide licenses for every paid application you may want to use. If your software requires a license, you are usually responsible for providing it. Before starting production work, check whether your software license can be used on a remote workstation.
Bring your own licenses
For paid tools, you may need to log in with your own account or activate your own license key. This can include 3D software, render engines, plugins, AI tools, or other production applications. When your work is done, remember to deactivate or release licenses if your software requires it.
Check license restrictions early
Some license systems are tied to specific hardware or network setups. These may not work smoothly on a cloud server. If you are unsure, test the license before starting an important project. This can save time, credits, and frustration.
Final thoughts
Xesktop gives beginners a practical way to access powerful GPU hardware without buying a new workstation. It works like a remote Windows desktop, but with cloud GPU power behind it.

As you become more familiar with the workflow, Xesktop starts to feel less like a separate cloud service and more like an extra workstation you can open when your local machine is not enough. The key is to build a clean routine, keep your files organized, test your setup before committing to heavier jobs, and shut things down properly when the work is done. With those basics in place, Xesktop can become a flexible creative workspace for anything.


































