Creative Commons Search to Relaunch on

The Creative Commons search engine will soon be part of, as Automattic will begin sponsoring several members of the CC Search team to maintain it. The engine currently offers over 500 million images, audio, and videos, under Creative Commons licenses or the public domain, aggregating more than 45 different sources.

Matt Mullenweg announced the acquisition on his personal blog, saying that CC Search would be “joining the WordPress project.” It is a major benefit to the community, providing a valuable resource for finding GPL-compatible images for use in WordPress-derivative products like themes and plugins. Mullenweg hinted at a long-term plan where deeply integrating CC search into is just the first step:

I am eager to give a new home to their open search product on in continued commitment to open source freedoms, and providing this community resource for decades to come. This is an important first step to provide a long-term, sustainable challenger to proprietary libraries like Unsplash.

The reference to Unsplash follows the company’s controversial licensing changes, where it abandoned CC0 licensing in 2017 after making a name for itself by offering images originally shared to the public domain. That body of work was hidden away by Unsplash’s refusal to use its API to differentiate these CC0 images going forward. In July 2020, the controversy was renewed after Unsplash launched its official WordPress plugin. Some users are apprehensive about the company’s willingness to change its license and terms in the future, especially after Unsplash was acquired by Getty Images.

Creative Commons search remains one of the few places to find CC0-licensed images that are compatible with the GPL. It will be interesting to see how this news of CC Search finding a new home on will affect Automattic’s relationship with Pexels, another image library with even more restrictive licensing than Unsplash. Access to Pexels was added to in 2018 and is also integrated with Jetpack.

“When I started CC Search, I always hoped it would become part of the infrastructure of the Internet,” former Creative Commons CEO Ryan Merkley  said. “Matt Mullenweg and I first talked about CC Search in 2018, and he immediately saw the potential. I’m so happy to see this happen. It’s great for WordPress, and great for the Commons.”

Mullenweg’s announcement said he anticipates CC search will be live and and running on in a few weeks. The new Automattic employees who were hired from Creative Commons will have their contributions sponsored by the company as part of the company’s Five for the Future commitment.


5 responses to “Creative Commons Search to Relaunch on”

  1. It would be great if the media library was better at supporting extensions. Currently, there’s a little bit of hacking required, and there’s a lot of plugins working in that area, most of the time it’s tedious to work around that.

    Also, it’s so strange to see so many image providers having their own images and their own plugins, most of which are unmaintained. I am hoping that instead of focusing on one provider, they would focus on providing an API to allow any provider to add a tab.

    I have built a plugin that does that, and I am planning to also allow other developers to use it as a framework for their own APIs. I am not sure if it’s just me, but sponsoring developers that aren’t working on WordPress-related projects most of the time isn’t really a recipe for success. Mainly, compatibility is pretty important. Especially with page builders.

    Finally, contributing to the core is also something complicated to do, the process is slow, and it’s far easier to contribute to a plugin instead. Especially since this is probably not going to be used by a majority, and it might be loaded for everyone, making the admin a bit slower.

    • It would be great if the media library was better at supporting extensions.

      Which extensions, in particular, are you thinking of?

      contributing to the core is also something complicated to do, the process is slow, and it’s far easier to contribute to a plugin instead.

      Sorry, I’m all questions today but I’m curious as to where around core contribution you feel these issues are? Of course, there’s a delay to any code change before it eventually gets released but are there delays anywhere else where you feel there shouldn’t be? And where do you see the complications? I’m both a core and plugin contributor myself, so I understand both sides of this.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: