Qwen Image 2.1 LoRA redistribution: notice file and Hangzhou courts
Sharing Qwen-Image-2.1 weights or a LoRA needs the license copy, modified-file notices and a Notice file; disputes go to the Hangzhou courts. Clause summary.

To redistribute Qwen-Image-2.1 or a derivative such as a merge or LoRA, section 3 of the Qwen Research License asks you to pass on a copy of the agreement, mark modified files with prominent change notices, and keep a Notice text file with the attribution line. Section 8 sends disputes to the People's Courts in Hangzhou City.
Clauses are quoted from the license file, read 2026-10-01; this is a summary, not legal advice. Whether a LoRA counts as a derivative work is for you or a lawyer to judge.
What must a redistribution include?
Section 3 is subject to section 2, so the non-commercial limit still applies. Within it, the conditions are listed below.
| Clause | Condition |
|---|---|
| 3(a) | Give recipients a copy of the Agreement |
| 3(b) | Mark modified files with prominent notices stating you changed them |
| 3(c) | Keep the attribution in a "Notice" text file distributed with the copies |
| 3(d) | You may add your own copyright statement and terms for your modifications, if the work otherwise complies |
What does the Notice file say?
Clause 3(c) quotes the line to retain: "Qwen is licensed under the Qwen RESEARCH LICENSE AGREEMENT, Copyright (c) 2026 Hangzhou Tongyi Laboratory Technology Co., Ltd. All Rights Reserved." Put it in a file named as the clause says, next to your weights or adapter.
Which law and court apply?
Section 8 says the agreement is governed by the laws of China, excluding the UN Convention on Contracts for the International Sale of Goods, and that the People's Courts in Hangzhou City have exclusive jurisdiction over disputes. Section 7 lets the licensor terminate for breach, after which you must delete and stop using the Materials.
Can I run a LoRA on Sume?
The cited Sume docs describe no LoRA upload or adapter field. The image docs say a request that sets a parameter the selected model does not list is rejected with 400 unsupported_parameter, and the catalog lists qwen/qwen-image and qwen/qwen-image-max ids rather than Qwen-Image-2.1. Redistribution duties above therefore apply to what you publish yourself, not to calls to the hosted ids. Terms for the hosted ids are not stated in these clauses.
Sources
Related posts
More in Developers
- remove.bg API rate limit: 500 per minute, weighted by megapixels
remove.bg allows 500 images per minute at about 1 MP, less for larger inputs. Sume limits requests per minute per key and sends retry-after on 429.
- remove.bg bg_color replacement: Sume RMBG gives a transparent PNG
remove.bg's API has bg_color and bg_image_url. Sume RMBG 1.0 takes only an image_url and returns a PNG with alpha, so the new background is a second step.
- remove.bg crop and roi parameters: what Sume RMBG does instead
remove.bg has crop, roi, crop_margin, scale and position. Sume RMBG takes an image_url only and rejects other fields, so cropping happens before or after.
- remove.bg PNG over 10 MP unsupported: Sume RMBG limits
remove.bg does not support PNG above 10 megapixels; use WebP or ZIP up to 50 MP. Sume RMBG returns PNG with alpha and caps compressed input at 20 MiB.
Written by Sume