Desktop GIFs: adding a GIF button to YouTube comments on the desktop site

A missing button on the YouTube comment box

The gap the extension fills is small and real. YouTube's mobile app can attach a GIF to a comment, but the desktop site has no button for it. Desktop GIFs adds one, next to the emoji button.

What the readme promises about the result is the important part, because it determines whether the extension is a gimmick or a real workflow. Everyone sees your GIF, because it is posted as an ordinary YouTube GIF comment and viewers do not need the extension to see it. You write around it, picking a GIF, keeping typing, then posting with YouTube's own Comment button. You search or paste, searching Tenor or pasting a Tenor link. You have favorites, starring the GIFs you use often and finding them behind one button. And there is nothing to set up: no account, no API key, no tracking.

That last point is what makes the design coherent. The extension is a UI shim. It does not proxy the comment, it does not intercept the post, and it does not need a server of its own. It finds a GIF, attaches it to the comment box, and then gets out of the way while YouTube's own button does the posting.

The repository is small and organised the way a browser extension usually is, with an extension/ directory holding the extension itself, a screenshots/ directory with images of the picker and the button, a tests/ directory and a tools/ directory. The readme notes that the screenshots show the extension's own interface on a test page standing in for YouTube's comment box, which is an honest caveat and a useful one, since it tells you the screenshots are not of the real thing.

The manifest is Manifest V3, and the badges state the browser requirements: Chrome 121 or newer, and Firefox 140 or newer. The releases are version 0.1.8, 0.1.7 and 0.1.6, all published on the same day, 2026-10-14.

Posting is broken, and the author says so first

The readme opens with a warning block, and it is the most useful thing in the document.

Posting GIFs is broken right now. Since 14 October 2026 YouTube refuses GIF comments sent from desktop. For most people every try fails, whether the comment has text or not, and whether it is a comment or a reply. The cause is on YouTube's side. Reinstalling, updating or picking another GIF will not fix it. Searching and the picker still work.

That last sentence matters, because it tells you exactly what still functions. The extension is not dead; the delivery step is.

The author then says he has not found a way around it yet, and asks that if you find one you open a pull request and he will review and merge it. What is known so far, and where to report it, is tracked in issue 93, and the request is to add to that issue rather than opening a new one.

This is unusual candour and it changes how you should read the rest of the documentation. The use instructions, the keyboard table and the update procedure are all still written as if the feature works, because they are written for a version of YouTube that accepted desktop GIF comments. The warning sits above all of it.

For an adopter, the practical reading is that this is a project in a blocked state, not a project in a broken state. The picker, the Tenor search, the favorites and the attachment to the comment box all work. What you cannot do today is complete the action the extension exists to enable. Whether to try it depends on whether you want to explore the mechanism, in which case the code and the issue tracker are the interesting part, or you need to post a GIF in a comment, in which case it will not happen.

The releases on the same day as the breaking change, three of them within a few hours, suggest the author was actively working on the problem when the deadline hit.

Installing from a ZIP, and what that costs you

The extension is not on the Chrome Web Store or addons.mozilla.org, so it is loaded unpacked from a ZIP, and the readme gives separate instructions for the two browser families.

For Chrome, Edge and Brave you download desktop-gifs-chromium.zip and unzip it, open chrome://extensions, turn on Developer mode, and click Load unpacked, choosing the unzipped folder with manifest.json directly inside it. YouTube tabs that are already open get the button without a refresh. The readme is careful about the scope of testing here: only Chrome is tested, and Edge, Brave and other Chromium browsers should work the same way.

For Firefox you download desktop-gifs-firefox.zip and there is no need to unzip it. You open about:debugging#/runtime/this-firefox, click Load Temporary Add-on and choose the ZIP. The consequence is noted in a callout: Firefox removes an add-on loaded this way when it closes, which is how Firefox treats every temporary add-on, so you repeat the load after a restart.

You can also run it from the source. The extension folder of the repository is the extension, and it loads in both browsers as it is, choosing that folder in Chrome or the manifest.json inside it in Firefox. Chromium browsers then list one harmless error about background.scripts, which the troubleshooting section covers.

The updating story follows from the installation method, and the readme is explicit about it. An extension loaded from a ZIP cannot update itself, so the GIF picker shows when a new version is out, with a Download link to the release. For Chrome you unzip the new ZIP over the old folder, replacing its files, and click the reload button on the extension's card in chrome://extensions, and your favorites are kept. For Firefox you load the new ZIP again. YouTube tabs that are already open switch to the new version without a refresh and keep what you typed and the GIF attached to a comment box.

There is one sharp edge for people coming from an older version. Coming from 0.1.5 or older, a GIF that was already attached is still posted by the old version, so you need to refresh the tab once if anything acts up. The close control on the notice hides it until the next version.

A separate detail worth knowing is where the favorites live. They are shared by all your YouTube tabs and are still there after a browser restart, in Firefox too, once the add-on is loaded again, and removing the extension from the browser deletes them.

Tenor search, paste handling and the keyboard table

The picker opens with Tenor's featured GIFs, and there are two ways to find a specific one. You can type to search Tenor, or you can paste a Tenor link, and the readme is specific that this covers a tenor.com/view page, a media.tenor.com file, or a bare Tenor ID.

Accepting a bare ID is a small touch that says something about how the extension was built. A Tenor page URL and a direct media file URL have completely different shapes, and handling all three means the user can paste whatever they copied from wherever they found the GIF, rather than having to know which form the extension wants.

To keep a GIF you point at it and click the star in its corner. The starred button next to the search field shows your favorites, and clicking it again goes back to the search. Clicking a favorite's star removes it.

The keyboard table documents two bindings, and the first is worth reading closely. Enter, in the search field, attaches the GIF when the picker shows exactly one, as it does after pasting a link. That is a deliberate constraint rather than a missing feature: pressing Enter with several results on screen does something else, presumably selecting, so the binding only fires in the unambiguous case. Ctrl+Enter is listed alongside it and, from the use instructions, is the shortcut for posting the comment once the text is written.

The use sequence itself is short. On a video or a Short you click Add a comment or Reply, click the GIF button next to the emoji button, click a GIF and it is attached to the comment box below your text, then you write or edit your text and click Comment or press Ctrl+Enter.

The text in the comment box is posted together with the GIF, and a comment can be just the GIF. To take the GIF off you click the cross in its corner, and picking another GIF replaces it.

Where Desktop GIFs is the wrong tool

There are four cases where this is the wrong choice, and three of them come down to the same fact.

The first, and the obvious one, is any task that involves actually posting the GIF. The readme is unambiguous that posting fails and that the cause is on YouTube's side. If your requirement is a GIF in a comment that you can see after posting, this does not currently do it.

The second is anything that needs to work on a schedule or without you present. The extension is a button you click in a comment box, and the whole interaction model assumes a person typing a comment. There is no queue, no automation and no server side, and the Tenor search is an interactive step. A tool that posts reaction GIFs from a bot or a script is a different program.

The third is a managed browser environment. An extension that must be loaded unpacked, that loses its favorites when it is removed, and that in Firefox has to be reloaded after every restart because Firefox removes temporary add-ons on close, is a tool for a personal machine. The readme is upfront about the Firefox behaviour, but the practical effect is that in an organisation that manages extensions centrally, this one has to be side loaded, and the Chrome Web Store route is not there yet.

The fourth is a platform where YouTube comments are not the goal. The extension is specifically about YouTube, and while the mechanism of injecting a button next to an emoji picker and attaching a media result to a text box is general, nothing in this repository generalises it.

On the alternative, the difference in approach against the obvious one, the YouTube mobile app, is instructive. The mobile app can attach a GIF, so if you are on a phone the extension is redundant. The extension exists for the desktop web, and it does the smallest possible thing: it adds a button, it fills the comment box, and it lets YouTube's own machinery post. The alternative is a script that drives the comment API directly, which would sidestep the button but would also mean handling authentication, the anti-abuse measures and the API's own rate limits, and it would break every time YouTube changed the posting flow. The extension's approach is to be broken in one specific place rather than fragile in all of them.

On maintenance and licensing, the facts are small. The last push was on 2026-10-14, the same day as the three releases and the same day the readme records YouTube breaking desktop GIF comments, which suggests the project is active rather than abandoned. The licence is GPL-3.0, and the readme links to the LICENSE file, which for a browser extension loaded from a ZIP rather than from a store is worth a look before you redistribute a modified build.

Editorial conclusion

Desktop GIFs suits someone who wants to search Tenor and attach a GIF while writing a comment on a video page, and it does not suit anyone who needs the posted GIF to appear, because the author states that posting is broken on YouTube's side and that no workaround has been found. Before you spend time on it, read the warning and issue 93 in the repository, and check the extension still loads in your browser version, since the readme states only Chrome is tested and the extension is not on the Chrome Web Store or addons.mozilla.org yet.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. rayytor/desktop_gifs on GitHub
4. README
5. Releases