Overview
TeamViewer connects two machines through an intermediary rendezvous rather than a direct route, which is why it works from behind a router, a corporate firewall or a mobile connection without anyone opening a port. For remote support that single property is the whole product: the person being helped reads out an identifier and a code, and the session starts.
The session itself is a full desktop with input, not a picture. Files move in both directions through a transfer panel or by drag and drop, the clipboard is shared, a remote printer can be redirected to the local one, multiple monitors are handled as separate views or one wide surface, and a session can be recorded to a file for a record of what was changed.
Unattended access covers the machines nobody is sitting at. A device gets a fixed identifier and a password, then appears in a device list ready to connect any time, with wake on network, remote reboot into safe mode and reconnect after restart. Sessions are encrypted end to end and can require confirmation on the remote side before control is handed over.
What it does well
Connects through anything
No port forwarding, no configuration on either router, works from behind restrictive firewalls and mobile connections.
Full session tooling
File transfer both ways, shared clipboard, printer redirection, remote reboot with automatic reconnect and session recording to a file.
Unattended access
Fixed identifiers with a device list, wake on network and reconnect after restart for machines with nobody in front of them.
Multi-monitor handling
Remote displays selectable individually or shown as one surface, with scaling that keeps text readable.
Encrypted sessions
End to end encryption with optional confirmation on the remote side before control is granted.
Changes in this build
- Connection negotiation improved, which shortened session start time on mobile connections.
- Video pipeline reworked for lower bandwidth at the same visual quality.
- Device list gained grouping and inline search.
- File transfer resumes after a dropped session rather than restarting.
- Fixed scaling on remote machines with mixed resolution displays.
What is in the package
- Full installer, 32-bit and 64-bit
- Portable run once module for the remote side
- Unattended access service component
- Session recording and playback
- Multilingual interface files, 30 languages
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 1 GB minimum |
| Graphics | Any GPU with a current driver |
| Storage | 200 MB free |
| Display | 1024 x 768 minimum |
| Network | Any internet connection, no inbound ports required |
Installation
- Extract the archive to a local folder.
- Choose the full install for your own machine, or the run once module for the remote side.
- Run setup and decide whether unattended access should be configured.
- Set a strong fixed password if unattended access is enabled.
- Start a test session to a second machine before relying on it.
Before you start
Unattended access with a weak password is the fastest way to lose a machine, use a long one.
The run once module needs no install on the remote side, which suits helping someone without rights.
Session recording is worth enabling on support work, it settles arguments about what was changed.
Questions about this title
Does it need port forwarding?
No, the connection is negotiated through an intermediary.
Can it connect to an unattended machine?
Yes, with a fixed identifier and password set on that machine.
Does it transfer files?
Yes, both directions, with resume after a dropped session.
Are sessions encrypted?
Yes, end to end, with optional confirmation on the remote side.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 (32-bit and 64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.