remmina.org

What is Remmina?

Remmina is a free, open-source remote desktop client for Linux and other Unix-like systems. It lets you connect from your own machine to another computer's screen and files, so you can work on a distant desktop as if you were sitting in front of it. The project describes itself as copylefted and libre: you can use, inspect, modify, and redistribute it.

What it connects to

Remmina's core strength is protocol breadth. It supports several common ways of reaching a remote machine through plugins:

• RDP — the standard choice for connecting to Windows desktops and Windows Server environments.
• VNC — widely used for cross-platform screen sharing and older or lightweight remote setups.
• SSH — for secure terminal access, and often tunneling other traffic.
• SPICE — common in virtualized environments, particularly with KVM/QEMU guests.
• X2Go — aimed at remote Linux desktop sessions, including lower-bandwidth links.
• HTTP/HTTPS — for web-based access scenarios.

Because these arrive as plugins, the practical question is which protocols your target machines actually expose. If you administer a mixed fleet, one client that speaks RDP, VNC, and SSH can replace several separate tools.

Who it suits

It fits system administrators, developers, and support staff who regularly jump between machines, and home users who want to reach a desktop at the office or a home server. The project notes availability across many Linux distributions and in dozens of languages, and it points to installation guides for various distributions. If your daily work happens on Linux and your remote targets are Windows or Linux, Remmina is a natural default.

It is less compelling if you are locked into a single vendor's ecosystem, need a heavily managed enterprise client with centralized policy controls, or work exclusively on Windows or macOS, where native or first-party clients may integrate more smoothly.

Features worth knowing

Beyond basic connections, the project highlights plugins, a kiosk mode, and multi-monitor support. Kiosk mode is the notable one for shared or locked-down machines: it restricts the interface so a user sees only the remote session. Multi-monitor support matters if you work across several screens and want the remote desktop to span them rather than sit in a window.

A practical next step

Decide by protocol and platform first. Write down what you need to reach — a Windows PC over RDP, a Linux box over SSH, a VM over SPICE — then check that Remmina's plugin set covers it. On a Debian- or Ubuntu-based system, the usual path is installing the package from your distribution's repositories and adding the protocol plugins you need. If you want to compare alternatives, RealVNC and Microsoft cover VNC and RDP tooling respectively, but Remmina's appeal is having them together in one libre client.

How do I install Remmina on my Linux distribution?

Remmina is usually easiest to install from your distribution's own package repository, not from a downloaded installer. The project states it is available in 50+ distributions and points to installation guides for specific Linux distributions, including YouTube video guides, so the version you get will depend on your distro and release.

Typical installation paths

• Debian/Ubuntu and derivatives: sudo apt install remmina. Add protocol plugins if you need them, since RDP, SSH, SPICE, VNC and X2Go are handled through plugins.
• Fedora/RHEL family: sudo dnf install remmina. Plugin packages may be separate.
• Arch/Manjaro: sudo pacman -S remmina.
• openSUSE: use zypper or the graphical software manager.
• Flatpak or Snap: useful when your distro's repository has an older build, but check that the protocol plugin you need is included or installable alongside it.

If your distribution's package is outdated but you do not want to build from source, a Flatpak or Snap build is often the pragmatic middle ground. If you need the newest protocol fixes and are comfortable managing dependencies, compiling from source is the other route; the project's installation page and distro-specific guides cover that.

A concrete first check

After installing, open Remmina and look at the protocol dropdown when creating a new connection. If RDP or VNC is missing, you likely installed the main package without its plugin packages. Search your package manager for "remmina" and install the plugin entries that match the protocols you use.

For official installation guidance, start at Remmina. If you are on Ubuntu, Ubuntu documents its package workflow; Fedora users can check Fedora.

Which remote desktop protocols does Remmina support and how do I choose the right one?

Remmina is a remote desktop client that supports several connection types through plugins: RDP, SSH, SPICE, VNC, X2Go, and HTTP/HTTPS. The right choice depends on what the remote machine is and what you need to do once you are connected.

Quick comparison

How to decide

Start with the remote operating system and service. If you are connecting to a Windows machine, RDP is usually the natural fit. If you are connecting to a Linux server mainly to run commands, SSH is lighter and faster than any graphical protocol. If you are managing virtual machines, SPICE is designed for that context. If the remote side only offers VNC, use VNC. If you need a graphical Linux desktop over a slow link, X2Go is worth trying before VNC.

Then consider what you need beyond pixels: clipboard sharing, file transfer, audio, USB devices, and multiple monitors. These are the details that often determine whether a protocol feels workable day to day, and they depend as much on the server configuration as on Remmina itself.

A practical next step is to install Remmina from your distribution's package manager, open the connection profile editor, and create one profile per protocol you need. Remmina's plugin approach means you can keep RDP, SSH, and VNC profiles side by side and switch between them without a separate client for each. The project's own site, Remmina remote desktop client, documents the available plugins and installation options for different Linux distributions.

How can I use Remmina to work from home or access my office computer remotely?

Remmina is a remote desktop client for Linux and other Unix-like systems that connects your local machine to a remote desktop or server, so you can see and control that computer as if you were sitting in front of it. For working from home, that typically means connecting to your office PC or a jump host using a protocol your workplace already supports.

Protocols and what they suit

Remmina supports several protocols through plugins, including RDP, SSH, SPICE, VNC, X2Go, and HTTP/HTTPS.

If your office computer runs Windows, RDP is usually the simplest route. If it runs Linux and you only need a shell, SSH is lighter and more reliable. VNC and X2Go are worth considering when you need a full graphical Linux desktop over a slower connection.

A practical setup sequence

1. Confirm what your office network allows. Many organisations require a VPN before any remote desktop connection, or expose only a gateway host rather than individual machines.
2. Install Remmina from your distribution's package manager, then add any protocol plugins you need.
3. Create a connection profile: choose the protocol, enter the hostname or IP address, your username, and the domain if your workplace uses one.
4. Set display options such as resolution and multi-monitor behaviour, and choose whether to share clipboard or local drives.
5. Save the profile and connect. Remmina can keep multiple profiles, which is useful if you regularly reach both a Windows desktop and a Linux server.

Remmina also offers kiosk mode, which locks the client into a single connection, and file sharing features, which matter if you need to move documents between home and the office without emailing them to yourself.

Whose experience this reflects

The page evidence describes Remmina's own features and positioning: it is copylefted and libre, available in many languages and distributions, and funded and translated by its community. It does not include benchmark results or a first-hand remote-work account, so treat the protocol guidance above as general advice rather than a claim about Remmina's measured performance.

Decision criteria

Choose Remmina if you want one client that covers several protocols and you value free, open-source software you can inspect and modify. If your employer mandates a specific commercial client or a browser-based gateway, Remmina may not fit that policy. Before relying on it for daily work, test the connection from outside your office network, check whether audio and USB redirection are needed, and confirm your organisation permits the protocol you plan to use.

A useful next step is to install Remmina, create one profile for the machine you need most, and verify it works over your VPN before adding more profiles.

What are Remmina's plugins and kiosk mode used for?

Remmina's plugins are the protocol and feature modules that let one client connect to different kinds of remote machines, and kiosk mode is a locked-down way to present that client to someone who should only see a remote session, not a full desktop.

Protocol plugins

The page lists RDP, SSH, SPICE, VNC, X2Go and HTTP/HTTPS as remote access protocol plugins. In practice, each plugin is what makes a particular connection type possible: RDP for Windows desktops and Windows Server sessions, VNC for cross-platform screen sharing, SSH for terminal access and tunnelling, SPICE for virtual machines, and X2Go for Linux remote sessions. HTTP/HTTPS support is useful for reaching web-based interfaces or gateways from the same tool.

The practical benefit is consolidation. A support technician, a developer with a mix of Linux and Windows hosts, or an administrator who has to jump between hypervisors can keep one connection manager instead of installing a separate client per protocol. The trade-off is that plugin quality and feature depth vary by protocol; if you depend on advanced redirection or multimedia behaviour, test the specific protocol rather than assuming all plugins are equal.

Kiosk mode

Kiosk mode is for situations where Remmina should behave like a dedicated appliance rather than a general-purpose application. Typical uses include a reception or shop-floor terminal that should only open a remote session, a lab machine shared by many users, or a thin client where the operator must not reach the local desktop.

The trade-off is deliberate restriction: fewer local options and less freedom for the person at the keyboard, in exchange for a predictable, tamper-resistant session. Before deploying it, decide what the user must still be able to do, such as switch monitors, print, or use USB devices, because those requirements determine whether kiosk mode fits.

Choosing between them

A useful next step is to install Remmina on one test machine, add a single connection for the protocol you use most, then try kiosk mode with that same connection to see whether the restrictions match your environment. The project also points to installation guidance for individual Linux distributions, which is worth checking because packaging and available plugins can differ between them. For a broader comparison of remote desktop clients, RealVNC covers the VNC side of the market.

Is Remmina free and open source, and what does its copyleft license allow me to do?

Yes. Remmina is free of charge and open source, and its own description goes further: it is “copylefted and libre,” meaning you may use, see, change, and share it. In practice, a copyleft license (Remmina is distributed under GPLv2-or-later) gives you four concrete freedoms:

• Run it for anything. Personal, workplace, or commercial use, on as many machines as you like.
• Study and modify the source. You can inspect how protocol plugins, kiosk mode, or multi-monitor handling work, and adapt them to your needs.
• Redistribute copies. Share the original or your modified version, including inside a company.
• Improve and publish your changes. If you release a modified version, copyleft requires you to pass on the same freedoms under the same license, and to make the corresponding source available.

What copyleft does not mean

• It does not forbid selling the software or charging for support; it only prevents others from turning your shared version into a proprietary, locked-down product.
• It does not cover every plugin or protocol library equally; third-party components can carry their own licenses, so check those if you plan to redistribute a bundled build.
• It does not remove trademark or attribution requirements.

A practical next step

If your goal is simply to connect to a work PC over RDP or VNC, install it from your distribution’s repository and start there — the project points to installation guides per Linux distribution. If your goal is to embed Remmina in a product or ship a customized build, first confirm the exact license of the version and plugins you use, then decide whether your distribution model can meet the source-sharing obligation. For comparison, other libre remote desktop clients exist, such as Vinagre or protocol-specific tools, but Remmina’s breadth across RDP, SSH, SPICE, VNC, X2Go, and HTTP/HTTPS is the main reason to choose it.