Is It Legal to Translate a Competitor's VSL? Copyright 101

Is translating someone's VSL to another language legal?

No, translating a competitor's VSL without permission is not legal, and the target language doesn't change that. Under 17 U.S.C. §106(2), the copyright owner holds the exclusive right to prepare derivative works, and §101 defines a derivative work as one "based upon one or more preexisting works," listing translation as its very first example. A VSL is a "motion picture or other audiovisual work" the moment it's recorded under §102(a), protected from creation with no registration required, per the Copyright Office's general FAQ.

The Copyright Office's own Circular 14 makes the point with an example this niche will recognize instantly: "a translation of a novel written in English into another language" sits on the same list as "a revision of a website." Swap English for Portuguese, Spanish, or Ukrainian and the legal analysis doesn't move — a translated VSL is a derivative work whether it runs on YouTube or inside a Telegram funnel.

The belief that circulates in swipe-file groups — that running a script through a translator turns it into "new content" because none of the original wording survives — misreads the statute. Derivative-work status doesn't turn on how much rewriting happened; it turns on whether the new work is based upon the preexisting one, and translation is the example Congress chose to list first.

Why does copyright cover translations as derivative works?

Because §106 reserves the derivative-work right to the copyright owner alone, and §101 defines that right broadly enough to sweep in anything "recast, transformed, or adapted" from an existing work — translation, dramatization, and motion-picture adaptation all sit in the same list. A VSL script translated into Spanish is "based upon" the English original in exactly the sense §101 describes, no matter how the translator phrases individual lines or how far the sentence structure drifts from the source.

There's a narrower point worth knowing if you ever try to defend a translated page as fully your own: §103(b) limits a derivative work's copyright to "the material contributed by the author of such work," not the preexisting material underneath it. §103(a) goes further — if the preexisting material was used unlawfully, the derivative earns no protection at all in the parts built on it. Translating without a license doesn't just expose you to the original owner's claim; it also means your translated version has no copyright of its own to assert if someone copies it from you.

What can you legally borrow when localizing a US offer?

You can legally borrow the idea, the mechanism, and the underlying facts, because copyright never reaches those — only the specific expression fixing them to the page. §102(b) states that copyright protection never extends to "any idea, procedure, process, system, method of operation, concept, principle, or discovery," and the Supreme Court held in Feist Publications v. Rural Telephone that facts, "whether alone or as part of a compilation," are "not original and therefore may not be copyrighted." A supplement's ingredient claims, a three-step offer structure, a scarcity mechanic — none of that belongs to the copyright owner.

The Copyright Office's FAQ and 37 CFR §202.1 add a related carve-out worth knowing: short phrases, slogans, and titles standing alone sit outside copyright's subject matter, even though the paragraph surrounding them does not. That's the honest dividing line between lifting a headline in isolation and lifting the paragraph beneath it. For the fuller mechanics of that boundary, see Swiping a VSL Legally: What You Can and Can't Copy.

In practice, the safer workflow is a teardown, not a translation: pull the funnel's structure, offer sequence, and claims into your own notes, then write fresh copy in the target language from those notes rather than from the source script. The funnel teardown template exists for that exact step — it forces you to separate what the page argues from how it argues it, which is the same separation §102(b) draws.

How do Brazilian and European affiliates adapt VSLs compliantly?

They rebuild rather than translate — same offer logic, same claims, new script, new voice talent, new footage where possible. That single substitution, a fresh recording instead of a dubbed or cloned copy of the original spokesperson, sidesteps two separate bodies of law at once: copyright in the audiovisual work, and whatever the spokesperson's home state recognizes as a right of publicity.

On the voice-cloning point specifically, Tennessee's ELVIS Act, effective July 2024, defines "voice" to include "a simulation of the voice of the individual" regardless of whether the actual recording is used, and creates liability for distributing the tool that produces the clone, not just for using it. California's Civil Code §3344 separately makes knowing commercial use of a person's voice without consent actionable, and a 2026 amendment added a fast injunction track requiring removal within two business days of service. Neither statute is a copyright law — they're a separate, state-by-state risk layered on top of the derivative-work question.

• Write the script from claims notes, not the source transcript, so the wording is independently created rather than translated.
• Cast and record a new voice actor for the market instead of dubbing or cloning the original spokesperson's voice.
• Source your own testimonials for the new market rather than subtitling the original ones, since a testimonial has to reflect an endorser who actually exists and actually used the product.
• The line for [copying a competitor's ad](/faq/is-it-legal-to-copy-a-competitor-s-ad-where-the-line-is) turns on the same expression-versus-idea test as the VSL question, just applied to a different asset.
• The line for [copying a landing page](/compliance/is-copying-a-competitor-s-landing-page-legal-the-line) follows the same logic again, applied to the page instead of the video.

What happens if the original offer owner finds your translation?

What happens depends heavily on whether the owner registered the copyright, and when. A US copyright holder can't file an infringement suit until the work is registered, per §411(a), and if registration happened more than three months after first publication, §412 strips out statutory damages and attorney's fees for the period before that registration, leaving only actual damages and profits. That timing detail is part of why some offer owners never sue over a translated funnel even when they'd win — proving actual damages from one translated copy running in another country often isn't worth the litigation cost.

Where statutory damages are available, §504(c) sets the range from $750 to $30,000 per work, rising to $150,000 if the infringement was willful and dropping to as low as $200 if it was innocent. Note the unit: per work. A translated VSL, its script, and its landing page can each count separately, which is why a single translated funnel can carry more exposure on paper than "one page" suggests.

How do you rebuild an angle for a new market from scratch?

Start by tracking the version you're modeling, not just whatever is live today, since most US offers iterate their VSL on a rolling basis and the structure worth rebuilding is whichever one has actually stabilized. Tracking a competitor's VSL changes week by week is the step most localizers skip, and skipping it means rebuilding around a script the owner has already abandoned.

From there, separate the page into what it claims and how it says it, write your claims list independently, and hand that list, not the transcript, to whoever writes your target-language script. If the rebuild uses testimonials, they need to be real: 16 CFR §465.2 makes it a violation to write, sell, or knowingly disseminate a testimonial that misrepresents whether the endorser exists or actually used the product, and that rule doesn't care which language the testimonial runs in.

The output should be independently created even where it lands on a similar offer mechanic — same hook category, same urgency device, same guarantee structure — expressed in your own sentences and your own footage. That's the version of swiping that survives scrutiny.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Daily Intel Service FAQ, VSL FAQ, Nutra Compliance FAQ, GLP-1 Marketing FAQ, What is a VSL?, and UTM parameter decoding guide. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.