Suno Says Your Public Domain Song Is Copyrighted: Why, and What Works

On 3 November a Suno user tried to make a version of Silent Night and was refused: the lyrics, the platform said, contain copyrighted material. They are substantially right on the law — the 1818 composition has been free for over a century — and still blocked, and fifty-nine replies later nobody in the thread had the full answer. Getting it wrong costs a seasonal release, because a Christmas track that cannot be generated in November cannot be distributed in December. So we read Suno's Community Guidelines and help centre at source, pulled the app's own error strings, checked two Copyright Office circulars, and cross-checked a published list of pre-1931 carols against what the thread reported generating. Two carols on the same list, one blocked and one not.

Filed 2026-11-09 Read 12 min Method How we work
In short
  • The short version: Suno's filter matches text, not rights. Its own help centre says a generation can fail for containing "Copyrighted or trademarked terms" — terms, not works — and no Suno document published anywhere grants a public-domain exception.
  • The app's own error strings grade their confidence: "Lyrics appear to contain copyrighted material", "Lyrics likely contain copyrighted material" and "Our moderation system wasn't sure about those lyrics" are three separate failure states in Suno's interface. A system that says "likely" is not making a rights finding.
  • The law is on the complainant's side and does not help. The Copyright Office treats a recording and a composition as two separate works (Circular 56A), and all US works published before 1 January 1931 are public domain (Circular 15A, April 2026). Silent Night, 1818, is not close.
  • The cross-check is the finding: We Three Kings (1857) and Hark! The Herald Angels Sing (1840) are both on the same pre-1931 public-domain list, and in the 3 November thread one was refused and the other generated. Publication date predicts nothing about whether the filter fires.
  • Three published routes reach a human and they do different jobs: support@suno.com for a generation you do not understand, the same address for an upload matched to a known recording "if you own the rights", and the Community Guidelines appeal for an enforcement action already taken. None is a pre-clearance switch.
Flat illustration on soft white-pink of a sheet-music page outline struck through by a hot pink rejection marker, framed by a nineteenth-century carol ornament border
A public-domain carol, refused. The filter matches text, not rights.

Search Suno copyrighted lyrics and the first two results will offer to get you round the block. That is the wrong shape of answer, and it is the only one on this page of results. The person who posted on 3 November was not trying to steal anything: "Silent Night, for example, has been public domain for a very long time, both the lyrics and the melody. Yet Suno just refuses to do it because 'It's copyrighted material'. And there's no way to tell it that it's wrong" (r/SunoAI, 3 November 2026, 59 comments).

They are right about Silent Night. They are wrong about there being no way to tell Suno it is wrong, and the reason they were blocked has almost nothing to do with the law they are citing. Both halves matter if you want a carol out before Christmas, so here is each one, from documents you can open yourself.

Why Suno says your public domain lyrics are copyrighted

The filter is not asking who owns the song. It is asking whether the text you submitted looks like text it has seen.

Suno says so itself, in a help article called Does Suno moderate songs? (edited 19 December 2025). Your song may not generate if it includes "The names of well known artists or people", "Copyrighted or trademarked terms", derogatory or defamatory terms, excessive profanity, or other inappropriate phrases (help.suno.com). Read the second item closely: the unit is a term, not a work. A string matcher that fires on terms has no way to know that the terms in front of it were first printed in 1818, and nothing in that list makes an exception for anything.

The best explanation in the thread came from a reader rather than from any ranking page, and it adds the part Suno does not say out loud. "Suno is afraid that the model will produce exact copyrighted arrangements it was trained on," wrote one commenter, going on: "your prompt (styles + lyrics) is conditioning for the model. So, if this conditioning is similar to one of the existing copyrighted recordings the model was trained on, there is a high probability that the model will produce this copyrighted version." On that reading the block is not about the carol at all — it is about the hundred commercial recordings of the carol that sit in the training data, and the fact that Silent Night plus "slow, choral, reverb" is a request for one of them.

That is a plausible account rather than a documented one, and it is the commenter's rather than ours. But it explains what the legal argument cannot: why a song being free should make a model more cautious, not less.

What Suno publishes about the filter, and what its own app says

There is one more source on the mechanism, and nobody writing about this has used it. Suno's web app ships its own interface strings, and they include the failure messages. Pulled from the bundle served with suno.com/community-guidelines on 9 November 2026, the lyric-copyright family has four members, plus one for uploads:

Error state in Suno's app The message as written What the wording concedes
failureLyricsCopyrighted "Your lyrics contain copyrighted material. Please change it and try again." The assertive version. This is the one the 3 November poster reported
failureLyricsAppearCopyrighted "Lyrics appear to contain copyrighted material." "Appear to" — a resemblance, not a finding
failureLyricsLikelyCopyrighted "Lyrics likely contain copyrighted material" "Likely" — a probability, stated as one
failureLyricsUncertain "Our moderation system wasn't sure about those lyrics, please try again" Explicitly no decision at all
failureKnownRecording "Our system matched this upload to a known recording. If you own the rights, please contact support@suno.com." A match plus a named route to a human

A system with three confidence tiers for one question is a classifier, and a classifier returns a score. There is also a failureTitleFlagged state — "Your title was flagged for moderation" — worth knowing if you have been pasting Silent Night into the title field as well as the lyric box: those are two separate checks on two separate strings.

A caution: these are product strings, not policy, so they tell you what states exist rather than how any one decision was reached, and we cannot know which message a given user saw. What they establish is that Suno's interface itself distinguishes "contains" from "appears to" from "wasn't sure" — and that the fifth row publishes the sentence the thread said did not exist.

Public domain means the composition, not the recording

Table of Suno's five lyric-copyright failure states and the message each one shows. failureLyricsCopyrighted asserts the lyrics contain copyrighted material; failureLyricsAppearCopyrighted says they appear to; failureLyricsLikelyCopyrighted says they likely do; failureLyricsUncertain says the moderation system was not sure; failureKnownRecording says the upload matched a known recording and names support at suno dot com
Four lyric-copyright failures, three of them hedged. A system that says “likely” is not making a rights finding. Free to reuse with credit to artifactr.net.

The complainant's legal reasoning is correct, and no page on this subject states it properly. A song is not one copyright. The US Copyright Office puts it plainly: sound recordings and musical compositions "are considered two separate works for copyright purposes," and "even though a sound recording is a derivative work of the underlying musical composition, a copyright in a sound recording is not the same as, or a substitute for, copyright in the underlying musical composition" (Circular 56A, revised March 2021). Its own example is Respect: the composition and Aretha Franklin's recording of it are two distinct works.

So "it has been recorded commercially many times" is not an argument against you. Those recordings are other people's property and always were; none reaches back and re-encloses the 1818 tune. The whole stack, as it stands in the United States this month:

Layer What it covers US status, November 2026 Rule
The composition Melody and lyric of the carol itself Public domain if published before 1 January 1931 95 years from publication; Circular 15A, revised April 2026
Old recordings, published before 1923 A specific performance on a specific disc Public domain since 1 January 2022 Music Modernization Act transition period ended 31 Dec 2021
Recordings published 1923-1946 Same Through 1925 are free; 1926 follows on 1 January 2027 95 years plus 5 more
Recordings published 1947-1956 Same Protected until 110 years from publication 95 years plus 15 more
Recordings fixed 1957 to 14 Feb 1972 Same Protected until 15 February 2067 Fixed statutory end date
Your new recording The take you generate or perform today Yours to exploit, subject to your Suno plan A new sound recording of a public-domain work

Duke's Center for the Study of the Public Domain summarises the same two cut-offs for this year in one line: "works from 1930 are open to all, as are sound recordings from 1925" (Public Domain Day 2026). The year bands come from the Copyright Office's own pre-1972 recordings page. Note the bottom row, because it is the one that pays: a new recording of a free composition is a work you can licence out. If you want the plan-by-plan version of what Suno grants over that audio, we have it in Suno's licence by plan tier.

Which Christmas songs are genuinely public domain

Table separating the composition from the recording. A carol's melody and lyric are public domain if published before 1 January 1931 under the 95-year rule in Circular 15A. Recordings published before 1923 have been free since 1 January 2022; those from 1923 to 1946 get 95 years plus 5; those from 1947 to 1956 get 95 plus 15; anything fixed from 1957 to 14 February 1972 runs to 15 February 2067. A new recording you make today is yours to exploit
Circular 56A treats a recording and a composition as two separate works. Free to reuse with credit to artifactr.net.

For the US the test is mechanical, and the Public Domain Information Project states it as the standard of proof for its own list: "to prove PD status in the USA, you MUST find a published copy of the song with a copyright date of 1930 or earlier." It publishes 47 carols it holds pre-1931 sheet music for (pdinfo.com). Twelve of the best-known, with the dates that list gives:

Carol First publication Reported in the 3 November thread
Silent Night 1818 (words 1816; English translation 1859) Refused
Hark! The Herald Angels Sing 1840 Generated, with an added chorus
We Three Kings 1857 Refused
I Heard the Bells on Christmas Day words 1864, music 1872 Generated after rewriting part of the lyric
Jingle Bells 1857 —
O Holy Night 1847 —
Joy to the World 1839 —
O Come All Ye Faithful 1841 (Adeste Fideles, 1751) —
The First Nowell 1833 —
God Rest Ye, Merry Gentlemen c. 1760 —
It Came Upon the Midnight Clear 1850 —
O Little Town of Bethlehem 1868 —

The third column is the finding. We Three Kings and Hark! The Herald Angels Sing are both on the same pre-1931 list, seventeen years apart, and in the same thread one was refused and the other went through — "This one worked for me last year based on Hark the herald angels sing… However when I tried We three kings it said it was under copyright." Publication date predicts nothing. Whatever the filter is scoring, it is not the carol's age.

Then there is the set that feels like a carol and is somebody's property. Ohio State University's library copyright guide publishes dates for seven of them:

Song Written Enters US public domain
Winter Wonderland 1934 2030
Rudolph the Red Nosed Reindeer 1939 2035
Frosty the Snowman 1950 2046
Jingle Bell Rock 1957 2053
Rockin' Around the Christmas Tree 1958 2054
Little Saint Nick 1963 2059
Holly Jolly Christmas 1964 2060

One honest caveat, because it is the kind of thing this site exists to catch: the lists that tell creators which carols are safe do not agree with each other. Ohio State dates Rudolph to 1939 and frees it in 2035; other references date Johnny Marks's song to 1949, which on the same 95-year rule puts it in 2045. We could not resolve that against a primary registration record, so we print no year of our own. The answer that holds either way is that it is not free now, and neither are White Christmas, The Christmas Song, Have Yourself a Merry Little Christmas or Let It Snow — none of which appears on any pre-1931 publication list.

What works when a carol you are entitled to use is blocked

Table of pre-1931 carols against what the 3 November thread reported generating. Silent Night, published 1818, was refused. Hark! The Herald Angels Sing, 1840, generated with an added chorus. We Three Kings, 1857, was refused. I Heard the Bells on Christmas Day generated after rewriting part of the lyric. Jingle Bells, O Holy Night, Joy to the World and The First Nowell were not reported either way
Two carols on the same pre-1931 list, one blocked and one not. Publication date predicts nothing about whether the filter fires. Free to reuse with credit to artifactr.net.

Three things were reported working in the thread, and they are not equally good. Ranked by what they leave you owning:

  1. Write your own lyric to the public-domain melody. The creator who covered I Heard The Bells On Christmas Day said it "was a headache and I had to write a certain percentage of new lyrics before it took," and ended up happier with the result. It is also the only route here that makes the output more defensible, because Suno's help centre says original lyrics stay yours whichever plan you are on (help.suno.com) — and they are the one element you can enforce.
  2. Change the arrangement request, not the words. If the commenter's account is right, the conditioning is the prompt as a whole. A carol asked for in a style no famous record of it uses is a different request from the same carol asked for in the style every famous record of it uses.
  3. Upload a melody you performed yourself. One commenter reported building a MIDI of the melody and uploading it; another found a hymn passed the upload check once trimmed to ten seconds or less. Suno does check MIDI files and publishes duration limits for the check, so this is a real path — but read our AI cover workflow first, because an upload brings its own rules about what you are allowed to put in.

What we are not going to publish is the trick. German trade press has reported that minor spelling changes often defeat the lyric check, and that is beside the point twice over: it does not give you a right you did not have, and Suno's Community Guidelines list "evasion of our controls" among the prohibited behaviours in the same breath as fraud and spam (suno.com). A block you have talked your way past is still a block, and the model's training-data problem is untouched by it.

How to tell Suno it is wrong: three routes, one gap

The thread's second claim — that there is no way to tell Suno it is wrong — is the half that is simply not true. Three routes are published, and the useful thing is that they do different jobs:

The gap is real and worth naming precisely, because it is the thing the poster actually wanted: none of the three is a pre-clearance route. There is no field where you assert that a lyric is public domain and have the generation go ahead. The thread argued about whether there should be — the proposal for a human-reviewed public-domain flag ran to -4 and -5, while the reply arguing it would be "abused to hell and back again, costing way more money to monitor and police up" was the highest-scoring comment in the thread at +5. That is not a consensus that the current filter is good. It is a consensus that the fix is expensive, which is a different thing and the one Suno appears to have priced.

Can you sell a public domain cover you made with AI?

Table of Christmas songs still in copyright and the year each enters the US public domain: Winter Wonderland written 1934 enters 2030, Rudolph the Red Nosed Reindeer 1939 enters 2035, Frosty the Snowman 1950 enters 2046, Jingle Bell Rock 1957 enters 2053, Rockin' Around the Christmas Tree 1958 enters 2054, Little Saint Nick 1963 enters 2059 and Holly Jolly Christmas 1964 enters 2060
The songs people most often assume are free, and when they will be. Sources disagree on Rudolph's date, so this guide prints no year of its own for it. Free to reuse with credit to artifactr.net.

Yes, and the clearance list is shorter than for anything else on this site — which is exactly why a seasonal carol is a sensible release. What you need, layer by layer:

What you need to clear For a public-domain carol Where it comes from
The composition Nothing to clear, nothing to pay Public domain; no publisher, no mechanical licence
Someone else's recording Not used — you are not sampling one Circular 56A's separate copyright stays theirs
Commercial rights to your audio Suno Pro or Premier "Songs made while subscribed are granted commercial use rights" (help centre)
Copyright in the result Thin, and Suno says so "Music made 100% with AI would not qualify for copyright protection… Writing the prompt does not constitute the creation of the song"
Your AI declaration at the distributor Required, and it is disclosure rather than a gate See getting the release out

The fourth row is the one to plan around: Suno's own guidance adds that "some distributors exclude songs that are not eligible for copyright protection" (help.suno.com, edited 4 September 2026) — one more reason to put a human-written lyric on a public-domain melody instead of generating both. Our guide to who owns an AI song covers what you can honestly promise a licensee.

On the money, a seasonal cover behaves differently from a normal release, and it is worth saying so plainly rather than quoting a per-stream rate. A carol has a four-week window, no algorithmic discovery to speak of, and an obvious second market: paid placement. Christmas advertising, seasonal television and retail reels all buy music on a brief, and a clean instrumental carol in a specific style is a briefable product. That is the case for pitching it for sync placements rather than waiting on streams, with direct sales as the other half — you keep the whole price and you own the buyer.

What clearing the filter does not fix

Two things, and both get conflated with this problem constantly.

It does not change what any platform says about your track. A generated carol is a generated carol whether or not the lyric box let it through. Spotify's AI disclosure and Apple's transparency tags are populated from what your distributor sends on delivery, not from anything in the audio, and no processing of the file alters them. If that is your actual question, it is a different one.

It does not make the audio finished. A solo carol is the least forgiving material a generator can be asked for — sparse arrangement, exposed vocal, long held notes, and a listener who has heard the tune ten thousand times. Artifacts that hide inside a dense mix sit in the open in a quiet one, so give the take one listen on headphones before you call it a release.

Frequently asked

Questions readers ask.

As a composition, yes, in the United States: Gruber's melody is 1818, Mohr's German words 1816, Young's English translation 1859 — all long before the 1 January 1931 cut-off stated in Copyright Office Circular 15A. What is not public domain is any recent recording of it, which carries a separate copyright of its own.

Because the check is a text match with a confidence score, not an ownership lookup. Suno's help centre lists "Copyrighted or trademarked terms" among the things that stop a song generating, and the app carries four lyric-copyright failure messages, two of which say only that the lyrics "appear to" or "likely" contain copyrighted material. Several people in the 3 November thread reported their own original material being flagged.

Nothing Suno publishes says so. The Community Guidelines, updated 1 October 2026, prohibit "uploading copyrighted material, reproducing existing songs, or using a real person's voice or likeness without permission" with no carve-out, and the phrase "public domain" does not appear on that page at all. One user in the thread quoted a support reply calling public-domain songs "generally discouraged" because their rights "belong to everyone" — one person's quoted email, not a published policy.

If the carol is genuinely public domain there is nothing to licence on the composition side. What you need is a commercial licence for the audio — on Suno, a Pro or Premier plan — and an accurate AI declaration at your distributor. Distributors do not ban AI music, but some exclude material that is not eligible for copyright protection, which Suno's own help centre warns about.

No, and the sources that say when it will be disagree. Ohio State University's library copyright guide dates the song to 1939 and frees it in 2035; other references date Johnny Marks's song to 1949, which on the same 95-year rule means 2045. We print no year of our own because we could not resolve that against a primary record. Either way it is not free now.

You can contest an enforcement action, which is not the same thing as a blocked generation. The Community Guidelines publish the appeal — "you can contest the decision, and we will review your appeal" — and the help centre separately invites you to email support@suno.com if you are unsure why content was flagged. Neither pre-clears a lyric.

It is the route people in the thread reported working, and the one that improves what you own. One creator covered I Heard The Bells On Christmas Day and "had to write a certain percentage of new lyrics before it took". Suno's help centre is unambiguous: "Regardless of which version of Suno you use, you retain ownership and rights to any original lyrics you input into Suno."

The verdict, in one sentence: Undetectr.

The boundary first, because this page is about one filter and it is easy to over-read. Clearing a generation block has nothing to do with how a platform labels your release: Spotify's AI disclosure and Apple's transparency tags are fed by what your distributor declares on delivery, and no audio processing changes either. What a tool can address is narrower and it sits at the other end of the job — whether the finished file is clean enough to ship, with no audible generation artifacts in a quiet carol where every one of them is exposed. That is what Undetectr does, and it is the only reason it appears on a page about a lyric matcher.