Can I modify the YouTube licenses in order to make a YouTube video about SO Content?
<p>I would like to create a YouTube video about content from StackOverflow. The licenses of SO do not seem to be compatible with the two licenses offered by YouTube as described in an answer <a href="https://meta.stackexchange.com/a/372442/1109146">here</a>. The same answer also indicates that it might be possible to modify the licenses offered by YouTube by simply putting the desired license into the description.</p>
<p>Am I really allowed to modify the offered licenses by YouTube to my liking?
If yes, on what basis?</p>

<p><strong>TL;DR:</strong> Technically, the SO and YouTube licenses are (probably) incompatible, so if you want to use copyrightable elements from SO in a YouTube video, you'll have to get permission from the original author.  Certainly it never hurts to ask, even if you might not strictly need it.</p>
<h2>You cannot change the YouTube license…</h2>
<p>When you upload a video to YouTube, you have to choose between one of (currently) two licensing options: &quot;Standard YouTube Licence&quot; and &quot;<a href="https://support.google.com/youtube/answer/2797468" rel="noreferrer">Creative Commons – Attribution</a>&quot;.</p>
<p>Neither of those licenses is exclusive, so you're certainly allowed to <em>also</em> license your video (to YouTube and/or anyone else) under some other terms.  (That's what <a href="https://meta.stackexchange.com/questions/372440/can-i-make-a-youtube-video-about-so-content/372442#372442">the answer you linked to</a> means by &quot;[stating] a license in your video description&quot;.)  But even if you do so, your original license grant to YouTube still applies <em>in addition to</em> the other license.  You can't just turn around and say that haha, no, you were just kidding, it actually doesn't.</p>
<p>(And if you try to do that, and actually get someone at YouTube to notice, their most likely response is to simply take your video down.  They're a huge company with millions of uploaded videos — they're not going to care about just one video, or even one channel, at least if it doesn't happen to be one of the handful of their most popular ones.)</p>
<h2>…and you must license derivative works of Stack Overflow content under CC BY-SA (not CC BY!)</h2>
<p>According to the Stack Overflow <a href="https://stackoverflow.com/legal/terms-of-service#licensing">Terms of Service</a>, &quot;subscriber content&quot; on SO (and other Stack Exchange sites, including this one) is <a href="https://stackoverflow.com/help/licensing">licensed</a> under the <a href="https://creativecommons.org/licenses/by-sa/4.0/" rel="noreferrer">Creative Commons Attribution–ShareAlike license</a> (CC BY-SA, version 2.5, 3.0 or 4.0 depending on when the content was posted).  The &quot;human-readable summary&quot; of this license, as shown on the linked page above, says (<strong>emphasis</strong> mine):</p>
<blockquote>
<p>You are free to:</p>
<ul>
<li>Share — copy and redistribute the material in any medium or format</li>
<li>Adapt — remix, transform, and build upon the material
for any purpose, even commercially.</li>
</ul>
<p>Under the following terms:</p>
<ul>
<li><p>Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.</p>
</li>
<li><p>ShareAlike — If you remix, transform, or build upon the material, <strong>you must distribute your contributions under the same license as the original.</strong></p>
</li>
<li><p>No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.</p>
</li>
</ul>
</blockquote>
<p>Note that this is <em>not</em> the same license as the <a href="https://creativecommons.org/licenses/by/3.0/" rel="noreferrer">Creative Commons Attribution 3.0</a> license (CC BY) offered as one of YouTube's licensing options.</p>
<p>In particular, the CC BY-SA licenses include the &quot;viral&quot; ShareAlike condition, which requires any derivative works based on the licensed work to also be licensed under the same CC BY-SA license (or one of a handful of designated &quot;compatible licenses&quot;).  So if you e.g. make a derivative video based on a CC BY-SA license Stack Overflow post, you must also license your video as CC BY-SA in order to be allowed to distribute it at all.</p>
<h2>…and you (probably) can't just dual-license your video to YouTube either</h2>
<p>In principle, there's an option that <em>might</em> be allowed under the terms of CC BY-SA, and would at least seem to follow the spirit of the license:</p>
<ol>
<li>Upload your video to YouTube normally, selecting &quot;Standard YouTube Licence&quot;.</li>
<li><em>Also</em> license your video to the public under CC BY-SA 4.0, e.g. by stating so in the video description or in the video itself.</li>
</ol>
<p>The idea is that, by explicitly releasing your derivative video to the general public under CC BY-SA, you've followed the requirements of the ShareAlike clause of the original Stack Overflow content's license (with some possible caveats regarding downloadability — see below).  The remaining question, then, is whether you're allowed to <em>also</em> license the video YouTube itself under their standard license.  And this, in turn, effectively boils down to the following question:</p>
<p><strong>Does the standard YouTube license allow YouTube to do something with your video that CC BY-SA doesn't already allow them to do anyway?</strong></p>
<p>If it doesn't, then the YouTube license grant is redundant: you're just telling YouTube &quot;sure, I give you permission to do all these things that you already can do under CC BY-SA.&quot;</p>
<p>If it does, however, then it's likely that you are not legally allowed to grant YouTube such permission to use your video, since it's (presumably) a derivative work of SO content it's based on, and thus may not be legally distributed without the original copyright holder's permission (which you and YouTube, again presumably, only have in the form of the CC BY-SA license).</p>
<p>The tricky part here is finding out exactly what the &quot;standard YouTube license&quot; actually says.  As far as I can tell, the actual terms of that license are buried in <a href="https://www.youtube.com/static?template=terms" rel="noreferrer">YouTube's Terms of Service</a>, and basically say the following (plus some other stuff regarding monetization and content deletion that do not seem relevant here; <strong>emphasis</strong> again mine):</p>
<blockquote>
<p>Licence to YouTube</p>
<p>By providing Content to the Service, you grant to YouTube a worldwide, non-exclusive, royalty-free, <strong>transferable, sublicensable</strong> licence to use that Content (including to reproduce, distribute, <strong>modify</strong>, display and perform it) for the purpose of operating, <strong>promoting</strong>, and improving the Service.</p>
<p>Licence to Other Users</p>
<p>You also grant each other user of the Service a worldwide, non-exclusive, royalty-free licence to access your Content through the Service, and to use that Content (including to reproduce, distribute, modify, display, and perform it) only as enabled by a feature of the Service.</p>
</blockquote>
<p>As far as I can tell (and keeping in mind that <a href="https://en.wikipedia.org/wiki/IANAL" rel="noreferrer">I am not a lawyer</a>), the &quot;licence to other users&quot; is innocuous — it's just a subset of the rights already granted by CC BY-SA.  (And none of these license grants are exclusive, so they don't prevent you from also granting a more permissive alternative license, such as CC BY-SA.)</p>
<p><em>Most</em> of the &quot;license to YouTube&quot; also looks fine to me, insofar as it basically just allows YouTube to distribute the video on your behalf, which, again, CC By-SA already allows anyway.  Mere mechanical modification of the the video for display purposes (such as downscaling it to a lower resolution, adjusting the playback speed, etc.) also does not seem particularly problematic to me, as such mechanical changes are generally not sufficient to create a new copyright, and thus your CC BY-SA license grant should extend to such mechanically modified versions as well.</p>
<p>However, there are a couple of terms in the license, which I've highlighted in <strong>bold</strong> above, that may be read as allowing YouTube to create further derivative works of your video (and thus, potentially, of the SO content it is based on) e.g. for promotional purposes, and to release these derivative works under a license <em>other than CC BY-SA</em>.  That would be a violation of the ShareAlike clause, and thus something that you may not give YouTube permission to do on behalf of the original SO content creator.</p>
<p>Would YouTube actually do that with your video?  Most likely not.  Could they?  Under that license, yes they could.</p>
<p>Also, there's a potential issue with the clause in CC BY-SA 4.0 that says (in section <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode#s3b3" rel="noreferrer">3(b)(3)</a>):</p>
<blockquote>
<p>You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.</p>
</blockquote>
<p>The problem here is that YouTube does not normally permit downloading videos, and <a href="https://en.wikipedia.org/wiki/Youtube-dl#RIAA_takedown_request" rel="noreferrer">has been known to send DMCA takedown requests</a> against software projects such as <a href="https://youtube-dl.org/" rel="noreferrer">youtube-dl</a> that attempt to circumvent this restriction.  As such, <em>only</em> distributing your video on YouTube could be interpreted as an attempt to prevent viewers of the video from exercising their right under CC BY-SA to download, redistribute and create derivative works of it.</p>
<p>Also, even if you e.g. included an alternative download link in your YouTube video description, that might not be sufficient to make you compliant with CC BY-SA, since you would still have granted YouTube a license to display and redistribute your video as they want, including in contexts that do not include your download link.</p>
<h2>…but your video might not be a derivative work in the first place</h2>
<p>However, all is still not lost, and in practice you might well be able to legally create a YouTube video based on a Stack Overflow post anyway.</p>
<p>The first, obvious, question is whether your video even counts as a derivative work in the first place.  <strong>Ideas cannot be copyrighted</strong>, and if all you're taking from the SO post is the <em>idea</em>, while not copying any specific phrasing choices or images or code, then your video won't be a derivative work under copyright law, and as such, you won't be bound by the restrictions of the CC BY-SA license.</p>
<p>Also, even including e.g. small snippets of code may be permitted without turning your video into a derivative work, if either the pieces are simple and generic enough not to meet the <a href="https://en.wikipedia.org/wiki/Threshold_of_originality" rel="noreferrer">threshold of originality</a> required for copyright protection, or if your use of them in your video is permitted under <a href="https://en.wikipedia.org/wiki/Fair_use" rel="noreferrer">fair use</a> (US), <a href="https://en.wikipedia.org/wiki/Fair_dealing" rel="noreferrer">fair dealing</a> (UK and commonwealth) or similar legal doctrines in your local jurisdiction.  In such a case, you're legally allowed to use them in your video <em>without availing yourself of the permissions granted by the CC BY-SA license</em>, and thus also without being bound by the restrictions included in that license.</p>
<p>The tricky bit here is that the boundaries of copyrightable originality and fair use are notoriously blurry and vary between jurisdictions, and it's very hard to be <em>sure</em> on which side of them your use falls on without an expensive and uncertain legal process.  When in any doubt, I would thus recommend not relying on them too much, at least not if your use is such that you could possibly imagine someone wanting to sue you over it.</p>
<p>By the way, <a href="https://physics.stackexchange.com/questions/111006/how-does-light-bend-around-my-finger-tip/111238#111238">one of my own answers on Physics Stack Exchange</a> was actually <a href="https://youtu.be/xnrXwpE2pMg?t=169" rel="noreferrer">turned into a YouTube video</a> by the &quot;It's Okay To Be Smart&quot; channel a couple of your ago.  What they did was exactly this: while they followed the style and structure of the answer quite closely in many respects, they took care to rephrase everything in their own words and to recreate all the demonstrations and diagrams.</p>
<p>Is their video legally a derivative work of my answer?  Maybe, marginally — some of their diagrams look <em>very</em> similar to mine, and some of the similarities just <em>might</em> be distinctive and original enough to be copyrightable.  But even if I wanted to sue them, this would be a tough argument to make and the outcome would by no means be certain.</p>
<p>I do wish they'd at least included my name and a backlink, though. :/</p>
<h2>…or the author of the original SO post might have multilicensed it</h2>
<p>Even if your video <em>is</em> a derivative work of an SO post, you might still be able to use content from the post in it without relying on the CC BY-SA license.  In particular, the same content might <em>also</em> be available under another, less restrictive license that you can choose to follow instead.</p>
<ul>
<li><p>In some cases, the post your quoting might directly include an <strong>alternative license notice</strong> e.g. as part of a code snippet, making that snippet (or whatever the extra license notice applies to) dual-licensed.</p>
</li>
<li><p>The code, images or text that you want to use may have been <strong>published elsewhere under a different license</strong> by its author.  For example, you might find a copy of it on one of the author's GitHub repositories (<a href="https://stackoverflow.com/questions/14420754/isaac-cipher-in-php/14428399#14428399">example</a>), or it might have been reposted on the author's blog.  Or, in the case of code, it might actually come from an open source project available under a permissive license (<a href="https://stackoverflow.com/questions/10940854/algorithms-for-visual-representations-of-checksums-e-g-sha/14447225#14447225">example</a>).</p>
<p>(BTW, both of the linked examples above are also examples of code with explicit license notices on SO).</p>
<p>In the absence of an explicit link in the post, Google can be your friend here.  Just make sure that any versions with a different claimed license really are licensed by the author and not just unauthorized third-party copies.</p>
</li>
<li><p>Some Stack Overflow users, <a href="https://stackoverflow.com/users/411022/ilmari-karonen?tab=profile">such as myself</a>, include a <strong>general dual-licensing statement</strong> on their user profile.  Mine, for example, currently looks like this:</p>
<blockquote>
<p>Please consider any (original) code I post to Stack Overflow and other Stack Exchange sites to be released under <a href="https://creativecommons.org/publicdomain/zero/1.0/" rel="noreferrer">CC-Zero</a> unless stated otherwise. You may do whatever you want with it and don't have to credit me in any way, although of course that would be nice.</p>
<p>In addition, to avoid ambiguity regarding the open source status of CC-Zero, you may also use, copy, modify, and/or distribute any original code I have posted on any Stack Exchange sites under the terms of the <a href="https://opensource.org/licenses/ISC" rel="noreferrer">ISC license</a> or any other OSI approved open source license, unless explicitly stated otherwise. If doing so, please use the copyright statement &quot;Copyright &lt;year of posting&gt; Ilmari Karonen&quot; if no other copyright statement is provided.</p>
</blockquote>
<p><sup>(Disclaimer: the statement above has been written by me for my own use, and has not been reviewed by a lawyer in any jurisdiction.  If you like it, you have my permission to adopt it verbatim or paraphrased for your own use, but I make absolutely no warranties regarding its legal effect or validity.)</sup></p>
</li>
</ul>
<h2>…or you could just ask for their permission</h2>
<p>Obviously, this is always an option, assuming that you can contact the author.  One simple way to do that is to post a comment on the post you want to reuse, asking for explicit permission to use it in your video and/or for an alternative license with more permissive terms.  Of course, it's up to the author whether or not they want to grant such permission.</p>
<p>At a minimum, something like the following additional permission should be sufficient (noting, again, that I am not a lawyer and that the text below has not been reviewed by one):</p>
<blockquote>
<p>In addition to the permissions granted by the CC BY-SA 4.0 license (and incorporating the definitions therein), You may upload Adapted Material based on this Licensed Material to third-party content sharing sites such as YouTube, and in doing so grant such sites an additional separate license to the Adapted Material and any Licensed Material contained therein, as required by their Terms of Service, provided that:</p>
<ul>
<li>You follow the License Conditions of the CC BY-SA 4.0 license (including the requirements to license the Adapted Material under CC BY-SA 4.0 or a BY-SA Compatible License, and to indicate this to recipients in a reasonable manner), and</li>
<li>You make a reasonable effort (e.g. by providing an alternative download link, if the content sharing site does not provide one by default) to allow recipients of the Adapted Material to download it in a manner and format that allows them to easily exercise their Licensed Rights to it.</li>
</ul>
</blockquote>
<p>or, in non-legalese:</p>
<blockquote>
<p>Yeah, sure, you can make a YouTube video based on my SO post, as long as you license it under CC By-SA and include a download link in the video description.</p>
</blockquote>
<h2>…and they might not care enough to sue you, anyway</h2>
<p>All things considered, it's extremely unlikely that anyone would bother to spend the time and money to actually sue you over a video based on a Stack Overflow post.</p>
<p>At worst, if they really didn't like what you did, they <em>might</em> decide to send YouTube a <a href="https://support.google.com/youtube/answer/2807622" rel="noreferrer">takedown request</a> for your video, since that's a relatively simple process.  At that point, assuming that YouTube acts on the request and takes your video down, you basically have three options:</p>
<ol>
<li>cut your losses, let the video stay deleted and hopefully be more careful next time,</li>
<li>contact the author of the source material and try to come to a mutually acceptable agreement with them (which, of course, you should ideally have done <em>before</em> posting the video), or</li>
<li>if you really believe that your use of the SO content was not a copyright violation, you can <a href="https://support.google.com/youtube/answer/2807684" rel="noreferrer">submit a counter-notice</a> to YouTube (who will forward it to the original claimant, who will then &quot;need to respond with evidence that they’ve taken legal action to keep the content from being restored to YouTube&quot; within 10 days).</li>
</ol>
<p>Of course, ideally you wouldn't ever let things get that far in the first place.  And the way to do that is to follow the advice above, and specifically to:</p>
<ol>
<li>not reuse copyrightable content when you can easily avoid it, but instead express your ideas in your own words, and with your own pictures and code;</li>
<li>when you do want to reuse content created by someone else, ask their permission if possible;</li>
<li>when basing your work on freely licensed content such as SO posts, try to follow the <em>spirit</em> of the license as far as possible, even if you cannot technically follow it to the letter;</li>
<li>in any case, always give credit where it's due, both for (potentially copyrightable) content and for (non-copyrightable) ideas and inspiration; and</li>
<li>generally try to be nice to people whose knowledge, creativity and hard work you're building on.</li>
</ol>
<p>Of course, following this advice won't prevent someone from suing you for copyright violation (although it <em>might</em> in some cases reduce their chances of prevailing, and/or the damages they can successfully claim if they do).  But it makes it less likely that they'll <em>want to</em>.</p>

<h1>You <em>cannot</em> unilaterally change the YouTube license...</h1>
<p>YouTube wants to have this content licensed to them in a particular way, so that they can access and use the content for whatever they want, however and whenever they want.</p>
<p>They have made the application of that license a condition of posting the content on their website. If you don't want it released to them or under their license, you can't use their site to share and promote it either. Fair deal for all involved - take it or leave it.</p>
<h1>... but, if it is your content, you can also license it however else you want to.</h1>
<p>You are not limited to licensing your content in one way and one way only. As long as you give YouTube the license they want, in exchange for using their site, you have upheld your side of the deal. This deal does not prevent you from also releasing the content under other licenses simultaneously.</p>
<p>This includes the right to license the same content differently</p>
<ul>
<li><p>in different jurisdictions e.g. allowing a company to distribute your film in Asia and Europe but not in North America.</p>
</li>
<li><p>for different people e.g. ABC can show your film privately but DEF may only show it in public venues.</p>
</li>
<li><p>for different purposes e.g. DEF may make a profit from ticket sales and advertising but ABC is not allowed to profit from showing it.</p>
</li>
<li><p>to create redundancy e.g. XYZ is given a license that lets them edit and reuse the film for anything as long as they make their work free to others, and another license that lets them do anything without any obligation, just in case one of the licenses is defective somehow.</p>
</li>
<li><p>to create revocability e.g. ABC is licensed for use within the specified calendar year only but DEF is licensed perpetually (or &quot;until I say otherwise&quot; or &quot;until they stop paying me the money I ask for&quot; etc.)</p>
</li>
</ul>

copyright licensing creative-commons