[wp-trac] [WordPress Trac] #64858: Add Threads as an oEmbed provider

[WordPress Trac]

#64858: Add Threads as an oEmbed provider
--------------------------------------+------------------------------
 Reporter:  pmestevez                 |       Owner:  (none)
     Type:  feature request           |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Embeds                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by pmestevez):

 Here is the filled out oEmbed questionnaire:

 >1. Is the service is popular enough for core developers to have heard of
 it before? Is it “mainstream?”

 Yes. Threads is a mainstream Meta product, not a niche service or side
 project. In Meta’s Q4 2025 earnings materials, the company said Threads
 had reached 320 million monthly active users, and that Q4 optimizations
 drove a 20% lift in time spent. That is the kind of scale and ongoing
 investment that makes it reasonable to treat Threads as a durable
 mainstream platform.

 > 2. If similar services are already supported, how does this service
 compare in terms of size, features, and backing?

 Threads compares favorably with other large social/discussion platforms
 already familiar to WordPress users. It is backed by Meta, has hundreds of
 millions of monthly active users, and exposes a dedicated oEmbed
 capability for public posts through official developer documentation.

 > 3. Does this service have an established social media presence?

 Yes.

 > 4. Is its oEmbed endpoint clearly established and properly documented?
 (Sometimes, they are just a developer’s pet project that may not be
 supported.)

 Yes. The initial endpoint was released in December of 2024 and the
 tokenless endpoint used by this proposed change was released in March of
 2026. The endpoint is documented at
 https://developers.facebook.com/docs/threads/tools-and-resources/embed-a
 -threads-post

 > 5. Does the oEmbed endpoint work with WordPress’ oEmbed auto-discovery?
 If not, could it be made to work with additional HTML tags or attributes
 being added to the allow-list?

 Given the limitation on non-allowlisted sites and the variety of Threads
 supported content types, the right solution seems to be adding Threads as
 a supported provider.

 > 6. Does the service make an effort to build relationships with
 developers, such as through robust APIs?

 Yes. We have an active developer community and up to date documentation.
 My team has hosted six developer events across the world in 2024 and 2025.

 > 7. How old is the service?

 Threads launched in July 2023, so it is no longer brand new. More
 importantly, it has now had time to demonstrate continued investment,
 feature expansion, and user growth rather than a short launch spike
 followed by abandonment.

 > 8. Does it have a well-established Wikipedia article? (Seriously.)

 Yes. https://en.wikipedia.org/wiki/Threads_(social_network)

 > 9. Has anyone written a WordPress plugin that leverages the service in
 some way, whether adding it as an oEmbed provider, creating a shortcode,
 or leveraging other APIs of the service? Do these plugins have any
 noticeable adoption or traction that would indicate usage and demand?

 Yes. There is at least one dedicated WordPress.org plugin, Social Post
 Embed, whose stated purpose is to support Threads embeds until they become
 part of WordPress core. There is also broader ecosystem demand through
 large embedding plugins such as EmbedPress, which has 100,000+ active
 installations and markets support for embedding social content from many
 sources.

 My team also works with a large number of publishers and we consistenyly
 hear demand for simpler ways to embed Threads posts.

 > 10. Is the provider frequently proposed?

 I don't have a lot of data points here but given the anecdotal evidence
 that my team has collected, the search results for tickets on this page,
 and the platform growth, I would say yes.


 Please let me know if this works or if I should expand in any of the
 areas. I hope this helps!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64858#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform