# More detailed chat invite link preview

**URL:** <https://forum.delta.chat/t/more-detailed-chat-invite-link-preview/5826>\
**Category:** Feature Proposal\
**Created:** [September 24, 2026, 5:33pm UTC](https://forum.delta.chat/t/more-detailed-chat-invite-link-preview/5826 "2026-09-24T17:33:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maphouse](https://forum.delta.chat/user_avatar/forum.delta.chat/maphouse/32/2853_2.png) [@maphouse](https://forum.delta.chat/u/maphouse)\
**Post date:** [September 24, 2026, 5:33pm UTC](https://forum.delta.chat/t/more-detailed-chat-invite-link-preview/5826/1 "2026-09-24T17:33:19Z")

</div>

Hi all, I’m wondering if it’s possible to develop link previews for link-based invites to dc itself ? Currently, sharing a link inviting a prospective dc user to chat with you is intimidating to most (massive cryptic url), so would benefit from some kind of embedded preview that displays _Message XYZ on Delta Chat_ or _Join the XYZ group chat_

EDIT, I realize there is a neutral _Message privately on Delta Chat_ preview, so my inquiry is more about including some of the existing slug info in this preview, e.g. if it’s a group chat, it could be a more opinionated message like _Join the XYZ group chat_. In theory, this is actually more transparent, signaling to the potential user what they’re getting themselves into before committing.

For individual chats and group chats, the sharer’s username is already in the share link. For group chats, the group name is also in the share link. So it could be something like:

1. _Message **XYZ** on Delta Chat_
2. _Join **XYZ** in **123** on Delta Chat_

---

<div class="post-metadata">

**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\
**Post date:** [September 24, 2026, 5:49pm UTC](https://forum.delta.chat/t/more-detailed-chat-invite-link-preview/5826/2 "2026-09-24T17:49:55Z")

</div>

I don’t think it is possible. [https://i.delta.chat/](https://i.delta.chat/) has this in the code:

```auto
    <meta property="og:type" content="website">
    <meta property="og:title" content="Message privately on Delta Chat">
    <meta property="og:image" content="https://invite.delta.chat/social.png">
    <meta property="og:url" content="https://i.delta.chat">

```

These tags are used to generate link preview, but they come from [i.delta.chat](http://i.delta.chat) web server and we don’t want [i.delta.chat](http://i.delta.chat) web server to ever see the group names or any private data. This is why all the data like group names, invite tokens etc. goes into URL “anchor”, after `#`. I have previously posted about it here (follow the link in that post as well):  
[Onboarding centralized? [add contact with vCard, besides i.delta.chat] - #2 by link2xt](https://support.delta.chat/t/onboarding-centralized-add-contact-with-vcard-besides-i-delta-chat/4867/2)

---

<div class="post-metadata">

**Author:** ![ian](https://forum.delta.chat/user_avatar/forum.delta.chat/ian/32/3164_2.png) [@ian](https://forum.delta.chat/u/ian)\
**Post date:** [September 24, 2026, 10:39pm UTC](https://forum.delta.chat/t/more-detailed-chat-invite-link-preview/5826/3 "2026-09-24T22:39:42Z")

</div>

The neutral open graph link metadata might be phrased to highlight that the [link](https://support.delta.chat/t/need-explanation-of-invite-uri-parameters/5727/2) can either initiate a direct message with a user, join a private or moderated group or subscribe to a broadcast channel. Improvements welcome, but an example could be:

> You have been invited to message a user, join a group or subscribe to a broadcast channel on Delta Chat
