Learn Vim at your own pace with my self-study Core Vim Course.

Learn more

Learn Vim at your own pace with my self-study Core Vim Course.

Accessing the system clipboard from Vim


Run time:

In some environments, Vim lets us access the system clipboard using the quoteplus register, "+. When this feature is enabled, we can use it with the delete, yank and put operations in much the same way that we use Vim’s other registers. Pasting from this register usually produces better results than using the system paste command in Insert mode.


This is an abridged quote from Vim’s documentation (see :h quoteplus):

CLIPBOARD is expected to be used for cut, copy and paste operations. … Vim uses CLIPBOARD when reading and writing the “+ register.

So long as your version of Vim has been compiled with support for the +clipboard feature, then you can use the "+ register to access your system clipboard.

Using the quoteplus register

The "+ register can be used much like any other register. For example, if you want to yank text from a Vim buffer into the system clipboard, you could use any of these commands:

command effect
{Visual}"+y copy the selected text into the system clipboard
"+y{motion} copy the text specified by {motion} into the system clipboard
:[range]yank + copy the text specified by [range] into the system clipboard

If you want to paste text from the system clipboard into your Vim buffer, you could use any of these commands:

command effect
"+p Normal mode put command pastes system clipboard after cursor
:put + Ex command puts contents of system clipboard on a new line
<C-r>+ From insert mode (or commandline mode)

The "+p command produces better results than ctrl-v

Using ctrl-v in Insert mode can produce strange artefacts, and for large sections of text it’s also noticably slower than pasting from the quoteplus register.

If your clipboard contains a multi-line range of text, then the ctrl-v command can produce strange results in Insert mode. Vim receives a stream of characters and interprets them just as though they were typed manually. If the autoindent feature is enabled, the Vim automatically adds spaces at the start of each line. When combined with the indentation already present in the code snippet, the result is that each line drifts farther and farther to the right. By contrast, if you use paste from the quoteplus register (e.g. using "+p or :put +), you can avoid this problem.

For large sections of text, the quoteplus register is noticably quicker than using ctrl-v in Insert mode. As an experiment, try this: copy the entire text of War and Peace into your clipboard. Open a new instance of Vim, switch to insert mode, and press ctrl-v (or cmd-v if you’re on a mac). Vim receives a stream of characters and inserts them into the document one by one. You might have to wait a while until you get control back! Now open another instance of Vim and run the command :put +. This time, the entire text should appear in your buffer instantly.

If you’re running GVim (or MacVim), then you shouldn’t experience any problems with the ctrl-v command. In the graphical environment, Vim can detect when a stream of input comes from the clipboard, and adjust its behavior accordingly. But when Vim runs inside the terminal, there’s no way it can tell whether the text is being entered manually or pasted from the clipboard.

What’s the difference between 'clipboard' and 'xterm_clipboard' features?

The +clipboard feature gives us access to the system clipboard through the "+ register. By "system clipboard”, I mean the one that we usually access with the system-wide cut, copy, and paste operations.

When Vim runs inside of xterm, the '+xterm_clipboard' feature gives us access to the primary selection through the "* register. This feature permits the following workflow: visually select text in Vim, switch to another app and use the middle mouse button to paste the text you selected. I’ve never used this workflow and I don’t find it appealing. One reason I use Vim is because I want to avoid using the mouse!

If your Vim was compiled with +clipboard and -xterm_clipboard (as my Vim is), then you can use "+ and "* interchangeably; both will access the system clipboard.

Make Vim use the system clipboard as the default register

If you’d like to make it easier to interact with the system clipboard, try out this setting:

set clipboard=unnamed

That tells Vim to use the quotestar register for all yank, delete, change, and put operations that have no register explicitly specified. In effect, the system clipboard becomes the default register. Beware that with this setting, the x command will write a single character to the system clipboard, overwriting whatever was in there previously.

If your version of Vim supports both the +clipboard and +xterm_clipboard features, then you might prefer to use this setting instead:

if has('unnamedplus')
  set clipboard=unnamed,unnamedplus

Read :h clipboard-unnamedplus for more details.

Further reading


Level-up your Vim


Boost your productivity with a Vim training class. Join a public class, or book a private session for your team.

Drew hosted a private Vim session for the shopify team that was one of the best workshops I have ever attended.

John Duff, Director of Engineering at Shopify


Make yourself a faster and more efficient developer with the help of these publications, including Practical Vim (Pragmatic Bookshelf 2012), which has over 50 five-star reviews on Amazon.

After reading it, I've switched to vim as my default editor on a daily basis with no regrets. ★★★★★

Javier Collado

Learn to use Vim efficiently in your Ruby projects

In association with thoughtbot, one of the most well respected Rails consultancies in the world, I've produced a series of screencasts on how to make navigating your Ruby projects with Vim ultra-efficient. Along the way, you’ll also learn how to make Ruby blocks a first-class text object in Vim. This lets you edit Ruby code at a higher level of abstraction. Available to buy from thoughtbot..