Browsers have excellent support for reading and writing the user’s clipboard, and this opens up possibilities for better, and more native like experiences on the web. On websites that use these APIs for helpful features, it feels natural to the user. On sites where it isn’t supported, it almost feels like a bug. In this series of articles, I’m going to demonstrate how to work with the clipboard.
Before We Begin…
Clipboard functionality on the web requires a “secure context”. So if you’re running an http site (as opposed to an https site), these features will not work. I’d highly encourage you to get your site on https. That being said, these features, and others like them that require secure contexts, will still work on http://localhost. There’s no need to set up a temporary certificate when doing local testing.
Also note that some browsers will manipulate the content of the clipboard when read. This is done for security reasons and you can disable it. I’ll demonstrate this later in the article.
The Clipboard API
The Clipboard API is the top-level object (navigator.clipboard) containing the methods to work with the clipboard. According to MDN, support is pretty much across the board:
In fact, the only outlier relates to being able to disable the security aspects mentioned above in Firefox and Safari. Outside of that, support is great.
Reading the Clipboard
Reading from the clipboard is handled by two methods:
readreadText
Which you use will depend on your particular use case. In theory, read would be the most flexible, handling any content, but if you know for a fact you only need to support text input from the clipboard, you should probably use the more specific readText format. I’m a fan of code that helps reduce my chance of mistakes so that’s what I’d recommend. Let’s start with an example of that.
First, I’ll use a bit of HTML:
<button id="readCB">Read Clipboard</button>
<div id="log"></div>Code language: HTML, XML (xml)The button will be used to kick off the code to read from the clipboard and I’ll use the <div> to show the results. Now the JavaScript:
let $log = document.querySelector('#log');
document.querySelector('#readCB').addEventListener('click', async () => {
let contents = await navigator.clipboard.readText();
console.log(contents);
$log.innerText += `From clipboard: ${contents}`;
});Code language: JavaScript (javascript)When the button is clicked, I try to read text from the clip. Note I said try. The first time the button is clicked, the browser prompts for permission:
If you need to revoke or change permissions…
There should be some UI in the browser bar area to do this. On Chrome it’s the little control icon which opens this:
The process of reading from the clipboard is async, so I’m using await to make that a bit simpler. Then, I log the contents to the console and write it out to the DOM.
Here’s a live demo, but please note that it may not work for you, because of the permissions prompts mentioned above. You can view this demo here and that will allow you to approve the permissions to make it work. It’s tricky with <iframe> demos — both domains need the permissions approved, but won’t prompt for them, and even then it doesn’t always want to work.
How well does it work?
If you have nothing on the clipboard, the code runs just fine, but the contents are an empty string. It was actually a bit difficult to figure out how to empty my clipboard. I initially tested by putting my cursor on an empty line in my editor and hitting CTRL+C, but that felt like a hack. This random article showed a command line prompt I could run on Windows that seemed to be more “official”. I used the suggested command and got the exact same result. No error, just an empty string.
Copying text works as expected, but note that if you copy HTML, and insert it into the DOM, it will be rendered as HTML. In my case, I’m using innerText so that’s not an issue.
Next, I tested “rendered” text, and by that I mean random text from a web page, ensuring I got styled text as well. As expected, I got just the text of the selection from the HTML. So for example:
Which ended up as:
CSS
MIXINS
STYLE QUERIES
Style Queries are Almost Like Mixins (But Mixins Would Be Better)
By CHRIS COYIER on July 12, 2024
Having a named block of styles to apply in CSS can be useful, and newfangled Style Queries are pretty close to that. We look at one use case here, how Sass did mixins better, and hope for a native solution.
I tried copying from Word and PDF and got the same type of result.
Cool — now let’s kick it up a notch!
Reading Multimedia Content from the Clipboard
As explained earlier, the read method can support any content, not just text. Switching to it is as simple as:
let contents = await navigator.clipboard.read();Code language: JavaScript (javascript)This method returns an array of ClipboardItems representing the fact that a user may have selected multiple different items. A ClipboardItem consists of:
types: An array of MIME types associated with the itempresentationStyle: This was one of the rare times when MDN failed to be helpful and I had to actually go to the spec. This property represents whether the pasted content should be considered as appended content or an attachment. You can imagine how an email client works where if you paste text, it just adds to the current email, but binary data is usually handled as an attachment to the mail instead. You don’t really need to worry about it as it’s only supported in Firefox. That being said, you can make up your own mind depending on the mimetype being used.
To get the actual contents you need to use the getType method, which feels oddly named. It takes a mimetype as an argument and returns a blob.
Now things get a bit more complex. Your application has to figure out what makes sense to do based on the data in the clipboard. Let’s consider a more advanced version of the previous demo:
document.querySelector('#readCB').addEventListener('click', async () => {
let contents = await navigator.clipboard.read();
for (let item of contents) {
console.log('Types for this item: ', item.types);
if (item.types.includes('text/html')) {
let blob = await item.getType('text/html');
let html = await blob.text();
console.log(html);
$log.innerHTML += html.replaceAll('<','<').replaceAll('>','>');
$log.innerHTML += '<hr>';
}
if (item.types.includes('text/plain')) {
let blob = await item.getType('text/plain');
let text = await blob.text();
console.log(text);
$log.innerHTML += text.replaceAll('<','<').replaceAll('>','>');
$log.innerHTML += '<hr>';
}
if (item.types.includes('image/png')) {
// modified from MDN sample
const pngImage = new Image();
pngImage.alt = "PNG image from clipboard";
const blob = await item.getType("image/png");
pngImage.src = URL.createObjectURL(blob);
$log.appendChild(pngImage);
}
}
});Code language: JavaScript (javascript)Remember: each item in the array has itself an array of mimetypes. This is very important because many places where you copy code (web pages, your IDE, etc.) may return both text/plain and text/html for an item. That’s… good, as it gives you options in terms of what you want to do. If you want to try to keep some of the original formatting, get the HTML. If you only care about the content, get just the plain text.
Here’s another live demo, this one handling multiple content types.
Copying from a PDF
Surprisingly, copying from a PDF will only return text/plain, even if you select an entire document and it has images. This makes some sense though. Check out the screenshot from Acrobat below, where I had run “Select All”:
As you can see above, the textual elements are highlighted, not the image. You can copy an image from a PDF, but you can have to click on it specifically.
Security Concerns and Sanitization
The MDN docs mention this in regards to reading from the clipboard:
Certain browsers may sanitize the clipboard data when it is read, to prevent malicious content from being pasted into the document. For example, Chrome (and other Chromium-based browsers) sanitizes HTML data by stripping
<script>tags and other potentially dangerous content. Use the unsanitized array to specify a list of MIME types that should not be sanitized.
The way around this is to pass a formats object to the read method that specifies an array of mimetypes the browser should not sanitize. Given a clipboard with potentially dangerous content, that means you would expect a different result from
let contents = await navigator.clipboard.read();Code language: JavaScript (javascript)versus:
let contents = await navigator.clipboard.read({ unsanitized: ['text/html'] });Code language: JavaScript (javascript)This was fairly difficult to test if I selected code that includes the <script> tag, it only reported text/plain as a mimetype. The only way I was able to verify this was in the MDN example where they kinda “force” the issue by writing to the clipboard as HTML. Honestly, I can’t see a reason to use this particular feature unless more ‘sanitized’ things turn up. I’d recommend just letting the browser clear it out if it needs to. But to be clear, if you copy code that includes the <script> tag, it will come in as text/plain and be read just fine.
Caveats
Though a user may have a file from the filesystem selected, if you try to read it from the clipboard, you get an empty array of results. I found this surprising as you can paste files into the browser and support reading them. We’ll get into that in the article on pasting.
Examples Use Cases
How about some examples to give you ideas of how you would use this in the real world?
Addresses
Sites making use of client-side maps (like Google Maps or Leaflet) could read from the clipboard and attempt to parse the contents as an address, and if found, focus the map. This will probably require the use of a Geocoding API to translate a freeform address into longitude and latitude points.
Google Maps on iOS (while not technically a web app) behaves this way. If you’ve given permission, if you happen to have an address on your clipboard you’ll see it as a one-click option right up top.
QR Codes
How about a TamperMonkey script that lets you take any block of text in your clipboard and turn it into a QR code? My buddy Todd Sharp literally built this the day after I wrote the first draft of this article. His work could be used in a regular web page as well to product QR codes from the clipboard.
URLs
If you knew the user had a URL on their clipboard, your app could offer to do something with it. Perhaps automatically add useful URL params, shorten it, or otherwise.
Can you think of any other use cases for reading from the clipboard? Admittedly, writing to the clipboard is generally a more common and useful ability, and we’ll get to that next.
Another look at this world from Alex Harri