Why a link breaks when you paste it into an email, chat or document

A pasted link breaks when the app that turns it into a clickable link guesses wrongly where it ends. A trailing full stop or bracket gets included, a space or line break cuts it short, or characters like spaces and accents are not encoded. Encode the address properly and keep punctuation away from its end.

The usual culprits

• Punctuation at the end. “See example.com/page.” — some apps include the full stop, and example.com/page. is a different address. Closing brackets cause the same problem, and some apps cut off brackets that belong to the link, as in Wikipedia-style addresses.
• Spaces. Links with spaces, such as file paths from shared drives, stop at the first space. Spaces must be encoded as %20.
• Line wrapping. Plain-text emails and some document exports wrap long lines, splitting a link in two. Only the first half becomes clickable.
• Smart quotes and dashes. Word processors may turn a hyphen into a dash or straight quotes into curly ones inside a link, producing an address that does not exist.
• Characters with special meaning. # starts a fragment, ? starts the query, & separates parameters, + can mean a space. If they are part of a value — say a search for “C#” — they must be encoded.
• Tracking or safe-link rewriting. Some email systems rewrite links through their own scanning service, and expired rewritten links stop working.

How to diagnose a broken link

1. Hover over or long-press the link to see the full address the app actually used.
2. Compare it with the original: look at the very end, and at any space or symbol.
3. Paste it into the URL Decoder, which shows the host, path and every query parameter separately, so a truncated value or a stray character stands out. If % signs remain after decoding, the link was encoded twice.

How to share links that survive

• Encode it. The URL Encoder turns spaces into %20 and accented characters into UTF-8 escapes while leaving the structure of the address alone. Use component mode for a single value going inside a query parameter.
• Put the link on its own line, or wrap it in angle brackets, such as <https://example.com/page>, a long-standing convention in plain-text email.
• Use link text in rich editors. Inserting a link behind words avoids wrapping and punctuation problems entirely.
• Keep it short. Remove tracking parameters you did not add yourself. When you do want campaign tags, build them with the UTM Link Builder so each value is encoded correctly.
• Always include https://. Without it, some apps do not recognise the text as a link at all.

Links to files on shared drives

Copied file paths such as \\server\Shared Files\Report.xlsx or a local C:\ path work only for people with access to that drive, and they contain spaces and backslashes that most apps will not recognise as a link. Share the cloud storage link instead, set to the right access level, and check it from an account that is not yours.

Links in PDFs and printed material

PDFs made from documents keep links clickable only if the export supports it, and long links can still break across lines on the page. For print, use a short, memorable address that redirects to the long one, or a QR code. Test by clicking every link in the exported file, not in the source document.

Mistakes to avoid

• Typing links by hand in a word processor with autocorrect on.
• Encoding an already encoded link, which turns %20 into %2520.
• Ending a sentence with a bare link followed by a full stop in plain-text email.

Checklist

• Starts with https:// and contains no raw spaces?
• No punctuation stuck to the end?
• Special characters inside values encoded once, not twice?
• Clicked and tested in the final format — email, PDF or chat?