{"id":64,"date":"2026-10-11T09:20:00","date_gmt":"2026-10-11T09:20:00","guid":{"rendered":"https:\/\/www.masters-tool.com\/blog\/?p=64"},"modified":"2026-10-08T03:04:42","modified_gmt":"2026-10-08T03:04:42","slug":"fixing-a-broken-paste-into-an-online-tool","status":"publish","type":"post","link":"https:\/\/www.masters-tool.com\/blog\/fixing-a-broken-paste-into-an-online-tool\/","title":{"rendered":"Fixing a Broken Paste into an Online Tool"},"content":{"rendered":"

TL;DR:<\/strong> When a paste into a web tool comes out garbled, suspect hidden characters, the wrong source view, or a box that split the text. Paste into a plain-text scratch area first, look at the ends and the line breaks, then paste once into the tool.<\/p>\n

The tool received what you pasted, not what you saw<\/h2>\n

Rich editors show you a cleaned view. The clipboard often holds a second version: HTML markup, soft hyphens, non-breaking spaces, curly quotes, or a byte-order mark. A converter, a formatter, or a calculator field then behaves as if your input were nonsense. The page is often right. The clipboard was carrying more than the sentence you highlighted.<\/p>\n

On Masters Tool, encoders, code formatters, and numeric fields fail this way in different costumes. An encoder will faithfully encode the hidden characters, so the output looks \u201ctoo long.\u201d A formatter will throw a syntax error on a line that looks fine. A numeric field will ignore the paste or keep only the digits before the first strange character. The fix starts by seeing the characters, not by switching tools immediately.<\/p>\n

A plain-text airlock<\/h2>\n

Paste first into a plain text note or an editor that can show invisible characters. Look at the start. A few junk bytes there will shift a script\u2019s first line or prepend garbage to a Base64 string that must stay intact. Look at the end. A trailing line break may be fine for code and fatal for a single-line token you intended to paste into a header. Look at line endings if the text came from another operating system. The words can be correct while the breaks are doubled, which makes a formatter \u201cwrap\u201d a file you thought was already short.<\/p>\n

If the plain-text version already looks wrong, do not paste it onward. Go back to the source and copy again from a different view. Copying from a rendered web page grabs the visible text. Copying from \u201cview source\u201d grabs entities and tags. Copying from a PDF grabs column breaks. Copying from a chat app may turn a hyphen into a line break. Choose the view that matches what the tool asked for, then copy that view only.<\/p>\n

Numbers and code break differently<\/h2>\n

Numeric fields reject units and grouping marks. A paste of \u201c1,250 cm\u201d into a centimeters box can become 1, or 1250, or an error, depending on the parser. Strip the unit and the thousands separator in the airlock. Leave a single decimal mark that matches the page. Scientific notation pasted from a word processor may have gained a space or a superscript that is no longer the letter e. Retype the exponent if the airlock shows anything other than a plain e or the page\u2019s expected form.<\/p>\n

Code formatters fail on smart quotes around strings, on an ellipsis character where three dots belonged, and on a comment marker that was turned into a bullet. Replace those in the airlock with straight quotes and ordinary punctuation. Then paste. If the formatter still fails, the problem is the code, and you can debug it without wondering whether the clipboard participated.<\/p>\n

The box itself can split the paste<\/h2>\n