Skip to main content
All CollectionsMails
Cleaning texts
Cleaning texts
Emma avatar
Written by Emma
Updated over a week ago

Here’s a piece of advice on how to “clean” your texts.

Oftentimes, the text you want to add to your newsletter comes from somewhere else, like Word or some other software, or maybe a website. When you copy a text, you also copy the background which contains hidden codes. These codes define for example the typeface, size, and color of the text, but other things as well. The underlying code that is copied with the text, can cause havoc and ruin your work when you insert it in your newsletter. It is designed for a completely different environment than your newsletter. Therefore, my advice is that you delete the underlying code before you paste the text into your letter.

How do I clean the text?

The easiest way to delete all underlying code, and clean your text, is to paste the text into a TXT file first.

My advice is that you always have this TXT file Notepad.txt on your desktop so you can quickly find it when you need to clean data. Step-by-step instructions are given here below. It looks more complicated than it is. You will notice after a while that it really is very easy and convenient.

1. Copy the text you want to add to your website.
2. Paste it in a blank TXT file (Notepad.txt).
3. Copy the text in the TXT file.
4. Paste the text in your newsletter.

To make the process even easier, use these excellent shortcuts:
Ctrl-A: select all
Ctrl-C: copy selected text
Ctrl-V: paste the text that was copied

If you combine the above instructions with these shortcuts, you will see that it takes no time at all to clean the data before pasting it in your letter.

1. Select the text you want to use, Ctrl-C (to copy)

2. Open a blank TXT file, Ctrl-V (to paste)

3. Ctrl-A (to select everything in the TXT file)

4. Ctrl-C (to copy it again, but now as plain data)
5. Go to your website and press Ctrl-V (to paste in the plain data).

Now you have the text in your newsletter without any underlying codes that could have caused a problem.

Did this answer your question?