BlendedBoris Blog: Simple Blockchain Ownership Registration

Seedream Lawsuit: What EVOX Suing ByteDance Over 7,095 Scraped Car Photos Means for Blender Artists Who Render, License and Sell Studio Images (2026) | Blended BORIS | Digital Art IP

EVOX Productions, a California company that has photographed cars for more than 30 years, has sued ByteDance, the parent company of TikTok, over its Seedream AI image generator. The complaint, filed on 29 October 2026 in the US District Court for the Central District of California and first reported on 16 November 2026, alleges that ByteDance copied 7,095 copyrighted car photos from EVOX's stock website to train Seedream.
EVOX says its server logs show the copying, and that Seedream can now produce car images that are nearly identical to its studio photos. It asks for the maximum statutory damages for each work, or its actual damages and ByteDance's profits, plus costs and legal fees. ByteDance had not responded publicly when the case was reported, and no court has ruled on anything yet.
The case matters to Blender artists for a simple reason. The pictures at the centre of it are clean studio shots of products on a white background, with soft shadows and carefully placed reflections. That is exactly what many Blender artists render for car makers, product brands, stock sites and marketplaces. This article explains what EVOX claims, what is still open, and what you can do now to protect renders you sell or show online.
TL;DR: the Seedream lawsuit

EVOX Productions v. ByteDance (case 5:26-cv-06428) claims ByteDance downloaded 7,095 registered car photos from EvoxStock.com around April 2026 and used them to train Seedream. EVOX says the model itself is an unauthorised derivative work and that its outputs copy EVOX's photos. It also claims ByteDance is responsible when users make copies. These are allegations: ByteDance has not answered in court yet. For Blender artists, the lessons are practical: register key renders before they are copied, keep server and shop logs, show small previews, and keep dated proof of your work.

What does EVOX claim in the Seedream lawsuit?

The 119-page complaint names ByteDance Inc. and ByteDance Ltd as defendants and brings two counts: direct copyright infringement and contributory infringement. Its key claims are:
  • The download. On or about 10 April 2026, a review of EVOX's server logs showed that ByteDance had accessed the servers of EvoxStock.com without authorisation and copied 7,095 images. Exhibit A lists every image with its copyright registration number.
  • The training. EVOX says ByteDance copied images from across the internet to build Seedream's training data. It points to ByteDance's own description of Seedream 4.0, which mentions "HTML-based data retrieval" to construct "high-quality editing data pairs".
  • The model. EVOX argues that Seedream is itself a derivative work, because the training turned the expressive parts of its photos into model weights.
  • The outputs. The complaint shows images made with Seedream 4.5 next to EVOX photos of a 2021 Audi Sportback, a 2021 Audi TT Coupe and a 2021 Chevrolet Silverado, and says they copy its compositions.
  • Contributory infringement. If ByteDance blames users for the copies, EVOX says ByteDance still knew this would happen, could prevent it, and made "a conscious decision not to prohibit, discourage, or even impede infringement by others" because users pay for Seedream subscriptions.

Who is EVOX, and why are car photos worth a lawsuit?

According to the complaint, EVOX has photographed nearly every passenger vehicle sold for more than 30 years and adds around 500 new vehicles a year. It owns the copyrights to more than two million photos and has registered more than one million of them with the US Copyright Office. It says it has invested about 56 million US dollars in the library, still earns millions of dollars a year from licences, and that a licence for a single image can exceed 1,300 US dollars. Its claim is that Seedream can now produce a similar image "for a few cents".
EVOX has been here before. In July 2026 it sued Stability AI, Runway, DeviantArt and Hugging Face, saying more than 100,000 links to its photos appear in the LAION dataset used to train Stable Diffusion. It has also filed claims against Google and Midjourney. The ByteDance case is different in one important way: it is not about links found in a public dataset, but about downloads that EVOX says it can see in its own server logs.
ByteDance has faced copyright pressure over its AI tools before. The Motion Picture Association sent it a cease-and-desist letter in February 2026 about Seedream 5.0 Lite and the Seedance 2.0 video model, and in August 2026 the two signed an agreement on guardrails for Seedream and Seedance. EVOX quotes that agreement and argues that ByteDance has shown a willingness to disregard the rights of smaller copyright owners.

Why should Blender artists care about a car photo case?

The complaint lists the creative choices EVOX says make its photos protectable: the angle of the car on a turntable, how far the wheels are turned, the lens and focal length, the camera height, overhead lighting, a white cyclorama background, soft-edge drop shadows, clean windows, the sheen on the tyres, and gray walls shaped to create a horizon line in the reflections. EVOX argues that the combination of these choices, as expressed in each photo, is what Seedream copies.
Anyone who renders products in Blender will recognise that list. You set the same things in your scene with a camera, area lights, a studio HDRI, a curved backdrop and a shadow catcher, then render in Cycles. The case shows two sides of the same risk:
  • Your renders can be training data. A clean studio render on a stock site, portfolio or marketplace page is exactly the kind of image an AI company wants. If it was taken from your server, logs may show it.
  • Techniques are not protected on their own. Copyright protects the expression in a specific image, not the idea of a white background or a three-light setup. EVOX's case depends on showing that Seedream copies its particular photos, not just a common studio look.
  • AI outputs can carry risk for you too. If you use an AI image tool for backplates, references or product shots, and the result closely matches someone else's photo or render, the person who publishes it can be exposed, whatever the tool's maker says.
Keep dated proof of every render you make.

If your studio renders are copied, scraped or claimed by someone else, the first question is who made what, and when. BlendedBoris adds a blockchain timestamp to your Blender work from inside Blender, giving you dated proof of authorship.

👉 Protect your Blender work with BlendedBoris

How strong are EVOX's legal theories?

None of EVOX's claims has been tested yet in this case, and courts have treated similar arguments in different ways. Here is where each theory stands:
EVOX theoryWhat EVOX saysWhere courts stand so farWhat it means for Blender artists
Copying the files7,095 images downloaded from EvoxStock.com without permissionHow training data was obtained matters: in Bartz v. Anthropic (2025) a judge treated pirated copies differently from lawfully bought booksKeep logs showing who accessed your files and when.
Training is not fair useSeedream was trained to replace EVOX imagesMixed: the Third Circuit found no fair use in Thomson Reuters v. ROSS; other courts have found fair use on their factsMarket harm to licensing is central. Show that you license your renders.
The model is a derivative workSeedream's weights are a compressed copy of the photosDisputed: a US judge dismissed this theory against Meta in 2023; it went forward in Andersen v. Stability AI; the UK High Court rejected a similar idea in Getty v. Stability AI, now on appealDo not rely on this theory alone.
Outputs copy the photosSeedream 4.5 car images match EVOX compositionsStrongest when outputs closely match specific works, as in our report on AI character copiesCollect side-by-side examples with dates.
Contributory infringementByteDance knows users copy and does not stop itDepends on knowledge and control; untested for this modelReport copies to the platform and keep the record.
Damages are another open question. EVOX asks for the maximum statutory damages for each work. US law allows up to 150,000 dollars per work for wilful infringement, which is why some reports have mentioned theoretical figures above one billion dollars. But by our count, Exhibit A lists the 7,095 images under 860 registration numbers, and the law treats all parts of a compilation as one work. EVOX argues that each image has its own economic value. How a court counts the works will make a large difference.

Why does registration timing matter so much?

EVOX can ask for statutory damages and legal fees because it registered its photos with the US Copyright Office. Under US law, you generally cannot claim statutory damages or attorney's fees for infringement that started before your work was registered, unless you registered within three months of first publication. Without registration, you have to prove your actual losses, which is hard when one render was copied into a training set of billions.
Our guide on how to register copyright explains the steps and options. The US Copyright Office also lets you register up to ten unpublished works in one application, which suits a series of renders before you publish them. Outside the US, registration works differently, so check our copyright basics for 3D artists and art registration guide. Whatever the country, you need to show the work is yours and when you made it.

What should Blender artists do now?

  1. Register your most valuable renders early. Do it before you publish or within three months, so statutory damages remain possible in the US.
  2. Keep server and shop logs. EVOX found the alleged copying in its server logs. If you sell from your own site, keep access logs and note unusual bulk downloads.
  3. Show small previews. Put watermarked, lower-resolution previews on public pages and deliver full-resolution renders only after a sale. Our guide to building a 3D portfolio covers how to present work without giving it all away.
  4. Use the opt-out signals. Add AI training rules to your robots.txt, as explained in how to opt out of AI training datasets and our report on the shared robots.txt signal, and use NoAI settings where platforms offer them.
  5. Put a no-AI-training clause in your licences. Say clearly that buyers may not use your renders or models to train AI. The sister blog explains dataset opt-out strategies and how to protect art from AI training.
  6. Watch for look-alikes. Run reverse image searches on your key renders and save dated screenshots of close matches.
  7. Ask clients what AI tools they use. If a client wants to feed your renders into an image generator, agree on it in writing first.
  8. Keep dated proof. Keep incremental .blend files, render passes and timestamps for each project, so you can show what you made and when. The sister blog lists your options when AI copies your art.

Where does this fit in the bigger picture?

Our sister sites covered stories this week about who can reach valuable files, and how:
Closer to home, the EVOX case joins a growing list of disputes over how AI tools are trained. Our reports on the OpenAI copyright lawsuit, the first generative AI case at the EU's top court and the Adobe and Disney AI alliance show the same question from different angles: who gets paid when creative work becomes training data. The sister blog's round-up of court decisions for artists gives more background.

Conclusion

EVOX's lawsuit against ByteDance is one of the clearest tests yet of what happens when an AI company is accused of taking images straight from a creator's own servers. Its claims are only allegations, and its broadest theory, that the Seedream model is itself a copy, has had a mixed reception in other courts. But its strongest points are ones any Blender artist can copy: registered work, server logs that show the download, side-by-side outputs, and a licensing business that shows real market harm. Register what matters, keep your logs, show previews rather than full files, and keep dated proof of every render.
Prove what you made, and when.

BlendedBoris records a blockchain timestamp of your Blender work from inside Blender, giving you dated proof of authorship for your models, scenes and renders.

👉 Get started with BlendedBoris

FAQ: the Seedream lawsuit

What is the Seedream lawsuit?

EVOX Productions, an automotive photography company, sued ByteDance in the US District Court for the Central District of California on 29 October 2026 (case 5:26-cv-06428). It claims ByteDance copied 7,095 of its copyrighted car photos to train the Seedream AI image generator.

What is Seedream?

Seedream is ByteDance's AI image generator, which creates images from text prompts. The complaint shows outputs from Seedream 4.5 and refers to ByteDance's description of Seedream 4.0.

How does EVOX say the images were taken?

EVOX says a review of its server logs on or about 10 April 2026 showed that ByteDance accessed EvoxStock.com without authorisation and copied 7,095 images. ByteDance has not responded in court yet.

How much money does EVOX want?

The complaint names no figure. It asks for the maximum statutory damages for each work, or actual damages and ByteDance's profits, plus interest, costs and legal fees. How many works count for damages is still open.

Has a court ruled on the case?

No. The complaint was filed on 29 October 2026 and reported on 16 November 2026. No ruling, answer or trial date has been reported.

Can someone copyright a studio lighting setup?

Not on its own. Copyright protects the expression in a specific image. EVOX argues that the combination of its choices in each photo is protected, and that Seedream copies those photos, not just a style.

Do I need to register my renders?

In the US, registration before infringement, or within three months of publication, makes statutory damages and legal fees possible. Other countries have different rules, but dated proof of authorship helps everywhere.

How can BlendedBoris help?

BlendedBoris adds a blockchain timestamp to your Blender work from inside Blender, giving you dated proof of authorship if your renders or models are copied, scraped or claimed by someone else.
2026-11-18 16:29 News