Update: These seems to be asked on Meta.Se as Please Improve supported URLs list for Embedded YouTube videos. It has very little support. I posted the below as an answer to try to improve views for the question. Please upvote it so that it gets some traction.

Sometimes youtube urls arnt parsed if it doesn't fit a specific format. Can we request that it be expanded?

Please add
Mobile links with the "m." subdomain

  • https ex:https://m.youtube.com/watch?v=71fWtJXEI0Q
  • http ex:http://m.youtube.com/watch?v=71fWtJXEI0Q

No Subdomain

  • https ex: https://youtube.com/watch?v=71fWtJXEI0Q
  • http ex: http://youtube.com/watch?v=71fWtJXEI0Q

Shortened by youtube's shortener

  • https ex: https://youtu.be/rEWaqUVac3M

Per a related question, Supported URLs for video embedding the current supported ones are:


While some unsupported ones are:

  • The shortened version works, though, just not with https.
    – Napoleon Wilson Mod
    Commented Mar 23, 2016 at 21:33
  • 1
    Related: Supported URLs for video embedding
    – Napoleon Wilson Mod
    Commented Mar 23, 2016 at 21:33
  • So yeah basically request to support the ones not supported yet.
    – cde
    Commented Mar 23, 2016 at 21:41
  • @cde you'd probably need to go raise this on meta.SE, then, since I assume it's a software change.
    – KutuluMike
    Commented Mar 23, 2016 at 22:16
  • @KutuluMike That question is about chat oneboxing. But, yes. This doesn't really affect only M&TV, so it's better on Meta.SE
    – Catija
    Commented Mar 23, 2016 at 22:19
  • 2
    The Meta post I was looking for is this one. Which, I think, is the question you're asking, though it's not as broad as this. Perhaps a request-supporting answer with the newer URLs that aren't currently supported?
    – Catija
    Commented Mar 23, 2016 at 22:23
  • There are also issues with embedding Youtube videos with timestamps, IIRC.
    – Walt
    Commented Mar 24, 2016 at 8:17

1 Answer 1


All sounds good; fixed in code - available after the next deploy (when the "rev" at the bottom of the screen is higher than "2016.3.23.3373")

  • Tested and confirmed with each of the example ones above. All are parsed properly. Thank you for the quick fix.
    – cde
    Commented Mar 26, 2016 at 2:28

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .