A YouTuber spends a decade building a channel with tutorials and reviews. At 63, worn out, he files for Social Security and stops filming. The old videos keep playing. Ad revenue trickles in monthly, and a licensing agreement signed before retirement pays out when one clip appears in a documentary. He assumes none of it counts because he is no longer working. Then a letter arrives. Social Security wants to know why his self-employment income resembles that of someone still on the job.
Variations of this scenario appear regularly in creator forums, among authors collecting book royalties, musicians receiving streaming payments, and photographers licensing old catalogs. To the creator, the income feels passive. To Social Security, it starts as countable until the records show otherwise.
The Rule That Actually Governs This Situation
Claiming before full retirement age (FRA) triggers the Social Security earnings test. In 2026, someone under FRA for the entire year can earn up to $24,480 before benefits are withheld. Above that limit, Social Security generally holds back $1 for every $2 of excess earnings.
For creators, when the work happened matters more than when the money arrives. In a taxable year after benefits begin, Social Security can exclude self-employment income that is not tied to significant services performed after the first month of entitlement. Revenue from an old video may therefore remain outside the test. The first year is more complicated because annual and monthly rules can overlap.
Royalties and other self-employment income are presumed countable until the creator shows otherwise. Publish dates, contracts, and channel records can establish that the work was completed earlier. Fresh uploads, sponsorships, editing, and regular channel management point toward current earnings; occasional activity unrelated to the revenue may not. If only part of the income stems from new work, only that portion should count. The question is not whether he logged in, but whether what he did helped produce the money.
Where the Line Gets Blurry
Consider two YouTubers receiving identical revenue after claiming at 63. One never logs in again. The other regularly responds to comments, rearranges playlists, updates older videos, and negotiates new licensing agreements. Their deposits may look the same, but the work behind them does not.
The first creator has a stronger case that the money flows from a library completed before retirement. The second is still helping the channel produce revenue. Records tying each payment to particular videos, contracts, and periods of work become the dividing line between old content and current self-employment.
How This Interacts With the Claiming Decision
Benefits withheld under the earnings test are not necessarily lost forever. At FRA, Social Security recalculates the benefit to credit months when payments were withheld, increasing the monthly amount going forward.
Claiming early still produces a smaller starting benefit. Filing at 62 can reduce the monthly amount by as much as 30% compared with waiting until FRA. For a creator whose archive may generate income for years, the decision should account for both the claiming reduction and the possibility that continuing work will trigger withholding.
What to Do Before the First Check Arrives
Two steps can make the creator’s retirement easier to prove:
- Separate the old library from any ongoing effort. Record the publication date of every revenue-producing asset, keep licensing agreements signed before claiming, and log any work performed on the channel afterward. If Social Security asks about the income, the timeline will already exist.
- Decide how active you plan to remain. If new uploads, sponsorships, or regular channel management will continue, treat the related profit as current earnings and plan around the annual limit. If production is ending, create a clean stopping date and document it.
Creator income does not always stop when the creator does. The videos can keep working after he retires. His records need to prove that he did.
Contact [email protected] for any questions or corrections.