# Register URL protocol handler for ThinLinc Client

**URL:** <https://community.thinlinc.com/t/register-url-protocol-handler-for-thinlinc-client/1775>\
**Category:** Community Support\
**Tags:** tlclient\
**Created:** [17 October 2025 12:12 UTC](https://community.thinlinc.com/t/register-url-protocol-handler-for-thinlinc-client/1775 "2025-10-17T12:12:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tpx-mk](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/tpx-mk/32/734_2.png) [@tpx-mk](https://community.thinlinc.com/u/tpx-mk)\
**Post date:** [17 October 2025 12:12 UTC](https://community.thinlinc.com/t/register-url-protocol-handler-for-thinlinc-client/1775/1 "2025-10-17T12:12:13Z")

</div>

Hi,

it would be nice if I were able to run the ThinLinc client by clicking on a link (e.g. _tlclient://user:pass@some.serveradress.domain_) and the client automatically fills out the provided fields (user, pass, serveraddress) and if possible tries to autologin with these values.

I know there is the WebAccess application, but it doesn’t provide the full functionallity of the client application (e.g. file transfer, direct clipboard support, etc.).

For Windows a protocol handler to run the client via some custom protocol prefix like _tlclient://_ is easily added into the registry:

```auto
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\tlclient]
“URL Protocol”=“”

[HKEY_CLASSES_ROOT\tlclient\shell]

[HKEY_CLASSES_ROOT\tlclient\shell\open]

[HKEY_CLASSES_ROOT\tlclient\shell\open\command]
@=“\"C:\\Program Files\\ThinLinc client\\tlclient.exe\" \"%1\"”

```

In Linux you could add the handler via a new `.desktop` file (e.g. `tlclient-handler.desktop`) in the `/usr/share/applications/` folder:

```auto
[Desktop Entry]
Type=Application
Exec=/opt/thinlinc/bin/tlclient %u
Name=ThinLinc Client Handler
Icon=thinlinc-client
MimeType=x-scheme-handler/tlclient;
Terminal=false
NoDisplay=true

```

The argument the handlers are sending to the application is always the full URL, so the client would need to parse this and fill out the fields accordingly.

Would be great if you implement something like this.

Thanks  
Martin

---

<div class="post-metadata">

**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\
**Post date:** [20 October 2025 21:41 UTC](https://community.thinlinc.com/t/register-url-protocol-handler-for-thinlinc-client/1775/2 "2025-10-20T21:41:01Z")

</div>

Hi @tpx-mk,

We actually have an entry in our Bugzilla on this theme here:

> **[8373 – Launching client from web portal is not convenient](https://bugzilla.cendio.com/show_bug.cgi?id=8373)**

For now, it is possible to use `.tlclient` files with the desired settings to launch the native client, provided you have the correct file associations set up on the client OS. These files are described in more detail here:

> **[Configuration storage — ThinLinc Administrator's Guide](https://www.cendio.com/resources/docs/tag/client_config.html)**
>
> Overview of how ThinLinc client configuration settings are stored and managed on Linux, macOS, and Windows systems, including file formats, directory locations, and registry usage.

As per bug 8373 though, this may not give a seamless experience as many browsers will simply download the file rather than opening it directly. So the URL-based approach is certainly an interesting idea.

Thanks for your input!