Logo

MonoCalc

/

Facebook Messenger Link Generator

Social Media
A username such as mypage, or a numeric Page or profile ID. Pasting an m.me, messenger.com or facebook.com address works too — the handle is taken out of it.
A short string the Page's messaging webhook receives when the chat opens, so you can tell a poster from a newsletter. It is not a UTM tag and the person chatting never sees it.
Used as the link text in the HTML snippet below. Left empty it reads “Message us on Messenger”.

Your Messenger link

Enter a Page username or ID above and the m.me link, its breakdown, a QR code and a chat mockup appear here.

About This Tool

Facebook Messenger Link Generator – One Handle, One Conversation

A Messenger link does one thing: it opens a one-to-one conversation with a particular account. That makes it different from almost everything else in the social toolbox. A share link posts a URL to an audience; a m.me link puts the reader in a chat window with you already selected as the recipient, whether they arrived from a poster, a receipt, an email footer or a button on your site. This Facebook Messenger link generator builds that link from whatever you have to hand, shows it broken into labelled parts, and renders it as a QR code — entirely in your browser, with no request ever sent to Facebook.

The shape of the link

The whole format is the host plus the account: https://m.me/yourpage. Everything after the slash is a Page username or a numeric Page or profile ID, and there is nothing else in the address unless you add a referral string. The desktop-web variant is the same account behind a different host and a /t/ prefix: https://www.messenger.com/t/yourpage. Both are ordinary https addresses, which is why they work in an email, a QR code, a printed flyer and a plain anchor tag alike.

Paste whatever you have

In practice nobody has the bare handle to hand. They have the address bar from the Page they were just looking at, which might read https://www.facebook.com/yourpage/posts/12345, or the older profile.php?id= form that carries a long number instead of a name. The tool accepts a bare handle, an @handle, an m.me link, a messenger.com/t/ link and any of the facebook.com shapes, and reduces each of them to the one handle the link needs. Extra path segments are dropped with a note saying what was dropped, so nothing disappears quietly.

What the ref parameter actually does

Adding ?ref=autumn-poster to an m.me link attaches a referral string that Meta forwards to the Page's messaging webhook when the conversation opens. That is how a business tells a chat started from a shop-window QR code apart from one started by a newsletter button, without asking the customer where they came from. Two things follow from that. It is invisible: the person opening the chat never sees it in their thread. And it is inert without a webhook: on a Page with no messaging integration connected, the value is simply carried and never read.

ref is not a UTM tag
A ref value is delivered to Messenger's webhook, not to your web analytics, and it does not appear in a campaign report beside utm_source and utm_medium. If you want to tag the landing page a link points at, build UTM parameters separately — the two systems answer different questions and mixing them gets you a value that neither side reads.

Where these links earn their keep

The QR code is the reason this format spread. A code on a table card, a delivery note or a product label turns a phone camera into a support channel with no app to find, no number to type and no form to fill in. An HTML button snippet does the same job on the web: the generated anchor carries target="_blank" and rel="noopener noreferrer", which is what stops the new tab from getting a handle on the page that opened it. The snippet here is shown as escaped text and is never inserted into this page's own markup — a link generator that runs the strings it builds is a link generator with a cross-site scripting hole in it.

What this tool deliberately will not tell you

No link is ever fetched, so a generated address means correctly formatted rather than checked. The handle may belong to nobody; the tool has no backend and cannot ask. Open your own link once before it goes on anything printed. For the same reason there is no prefilled-message field: the claim that m.me accepts message text is common but was not confirmed against Meta's own documentation, and a field that silently does nothing is worse than no field. No fb-messenger:// app link is produced either, because native schemes differ between platforms and change without notice, while the https link already hands off to the app when it is installed.

Handles, IDs and the difference between them

A username is the vanity name a Page has claimed — letters, numbers and periods, no spaces or dashes. A numeric ID is the long string of digits that identifies an account whether or not it has claimed a name, and it is what profile.php?id= carries. Either works in the link. The one to prefer is the username, because it survives being read aloud and typed in by hand, while a fifteen-digit ID does not.

Frequently Asked Questions

Is the Facebook Messenger Link Generator free?

Yes, Facebook Messenger Link Generator is totally free :)

Can I use the Facebook Messenger Link Generator offline?

Yes, you can install the webapp as PWA.

Is it safe to use Facebook Messenger Link Generator?

Yes, any data related to Facebook Messenger Link Generator only stored in your browser (if storage required). You can simply clear browser cache to clear all the stored data. We do not store any data on server.

How does the Facebook Messenger link generator work?

You type a Page username or a numeric Page or profile ID — or paste an m.me, messenger.com or facebook.com address and let the tool pull the handle out of it — and the link is assembled in your browser through the URL and URLSearchParams APIs. You get the short m.me link, the messenger.com thread link for desktop, an HTML button snippet and a QR code, plus a breakdown of the finished URL part by part. Nothing is ever fetched: Facebook is not contacted at any point, so nothing about the Page you are linking to leaves your device.

What is an m.me link?

m.me is Messenger's short link host, and everything after the slash is the account being addressed. Opening https://m.me/yourpage starts a one-to-one conversation thread with that account rather than sharing anything to a feed. That is the difference between this tool and a share-link builder: a share link posts a URL to an audience, while an m.me link opens a chat window with you already selected as the recipient.

Does the link work if the person does not have the Messenger app?

The link is an ordinary https address, so it opens in a browser like any other. On a phone with Messenger installed, tapping it typically hands off to the app; without the app it stays on Messenger's web page, where the person may be asked to sign in to Facebook before the conversation opens. That handoff is Meta's behaviour and not something this tool controls, which is also why no fb-messenger:// deep link is generated here.

What does the ref parameter do, and who sees it?

ref is a referral string that Meta forwards to the Page's messaging webhook when the conversation opens, so the Page can tell which button, poster or campaign started the chat. The person opening the link never sees it in their conversation, and it does nothing at all unless the Page has a webhook connected. It is not a UTM tag and it will not show up in your web analytics — use a UTM builder for that, and keep the two apart.

Does this work for a personal profile or only for a Page?

The link format is the same either way: a username or a numeric ID after the host. In practice the messaging behaviour differs, because features like the ref parameter and the webhook that receives it belong to Pages rather than personal profiles, and a personal account's message settings decide whether a stranger's message lands in the inbox or in message requests. The tool builds a correctly formatted link in both cases and does not attempt to predict which of those two an unfamiliar account will do.

Why is there no prefilled message box?

A text parameter that prefills the composer is widely claimed to work on m.me links, but that claim could not be confirmed from Meta's own Messenger Platform documentation when this tool was built. A field that silently does nothing is worse than no field, so none is offered and the chat mockup shows no prefilled bubble. If you need text carried along with the link, put it in the post, email or poster that the link sits in.