Registered characters

In short

Keep the same face across every shot, including on video models that refuse photoreal faces
Generate your character in Lorvara, or bring one you made in Midjourney or another AI model and declare it AI-generated
Add them to a Cast entry as views or a turnaround sheet, on a project set to a Seedance video model
Lorvara registers them for you in seconds, costing no credits. You never do this by hand (You do not register anything by hand)
From then on that face is accepted where an ordinary reference picture would be declined (What registering does)
A picture Lorvara generated registers on its record; one made elsewhere registers on your declaration that it is AI-generated (Which images)
One rule with no exceptions: a character that reads as under 18 is never registered, however the picture was made (under 18)

What registering does

Seedance declines a photoreal face in a reference image at submit time (see the face note). The picture never reaches the model, so the character never arrives.

Registering takes the same picture and stores it with our model aggregator, who serve Seedance, as a named asset. The generation then names the asset instead of sending the picture, and the face check does not stand in the way. The reference is the same file; what changes is how it travels.

The measured result: the same sheet sent as a picture is declined, and sent as a registered character is accepted, and the character in the finished clip is the character on the sheet.

You do not register anything by hand

There is no register button and no registration dialog. The act that registers a character is the act you already do: a reference sheet or a set of views landing on that character’s card, and the cast being confirmed.

You can do that act where the picture is, without opening the brief: Use as Mara’s sheet on a reference row’s card in Scenes & Shots, Cast reference on a result card in the Studio, the cast chip on a character reference in the Studio’s Refs panel that did not come from the brief, Make this a character on a shot’s reference when the brief does not yet hold the name, and Use as a cast reference on a generation you pick in Add Ref for a character. Each files the picture on the cast, confirms it and starts the registration, and tells you what happened, including when nothing needed to happen (a project whose video model is not a Seedance one) or when the rights confirmation is still wanted. On a team, any member with a full seat can do this on the team’s brief.

A picture you made elsewhere, a Midjourney download for instance, takes the same control. Lorvara cannot see where such a picture came from, so the dialog asks you to tick once that it is AI-generated and that you hold the rights to use it; the picture is then filed on the brief and registers like any other. Without the tick nothing is filed.

Two things have to be true:

The project’s video model is a Seedance one. That includes a project that has not chosen a video model, because Seedance 2.5 is the default. Nothing is sent anywhere on a project set to anything else. Switch a project to a Seedance model later and its cast registers then, in the background.
You have confirmed the rights, once. The first time a cast on such a project is ready to register, the block asks for one confirmation:

I confirm the characters I register are AI-generated, and that I hold the rights to use them.

It is asked once for the account or team that holds the brief, not per image and not per character, and any full seat on a team can give it. It is a recorded event, not a permission: a confirmation given by a colleague who later leaves the team still stands, and the characters it covered keep working. If the wording ever changes, you are asked once more, against the new words.

After that it runs in the background. Registration costs no credits.

What the card tells you

One line under the character’s name, and a small dot on each reference tile. The words are Lorvara’s, translated from our model aggregator’s statuses (Processing, Active, Failed):

The line	What it means
Registering for Seedance · 1 of 3	In progress. The line moves as each image lands, without a reload.
Registered for Seedance · 3 of 3 · 23 Sep	Done, and the date it was last confirmed with our model aggregator.
Registered for Seedance · 2 of 3 · 1 not registered, then the reason	Partly done. The one that did not go carries the reason.
Not registered for Seedance, then the reason	None went, and the line says why.

A failure shows the aggregator’s own reason, under Lorvara’s sentence saying the image was not accepted. It is shown as it was given, not translated. Hovering a tile shows the reason for that tile.

There is a Retry on the character when a retry could help: the aggregator having a bad minute, or something you have since changed. A failure whose reason is about the picture is not retried automatically, because regenerating the picture is usually the fix.

A picture made elsewhere waits for your declaration. Lorvara cannot see where an uploaded picture came from, so its line says it needs you to declare it AI-generated, and a checkbox under its tile does that. You see the checkbox when you attach the picture, and on any picture already on the card. Tick it and the picture registers. Retry is there too, for after you have declared.

The same declaration is offered where Seedance refuses a face. When a Seedance shot fails because a reference shows a face, the Studio’s failed panel reads “A reference shows a face” and offers Register … as a character on the refused picture. It runs the same steps as Cast reference: Lorvara first checks whether the picture is one of your generations, and asks for the declaration only when it is not, saying “Lorvara has no record that this picture was generated here, so it registers for Seedance on your declaration.” The tick is the one described above; there is not a second kind. Registering does not send the shot again. The panel says so, “Registering does not resend this shot.”, and goes on to say that the character registers at the video provider, Processing and then Active, and that you then send again.

A character refused as under 18 gets no Retry. Trying again gives the same answer, so the line says why and offers nothing to press.

A verdict belongs to the picture it judged. Replace a sheet and the old one’s dot and reason go with it. The new picture has no verdict until the cast is confirmed and it registers.

Coming back a month later, the card still says Registered · 6 of 6 · 3 Sep. That is a cached fact with its date on it, which is why the date is shown. Nothing is checked with the aggregator when you open the page; it is checked at send, at no cost in credits, when the fact is more than a day old, and if the asset has gone, Lorvara re-registers from the file it still holds rather than failing your generation.

Which images can be registered

Two ways in, and Lorvara records which one each picture took.

Proven. Lorvara generated it, with nothing uploaded anywhere in its history. Not the last step, the whole chain: an image generated from a reference that was itself generated is fine. Lorvara checks this on the server from its own records, so you do nothing.

Declared. Everything else: a character you made in Midjourney, or any other AI model, and uploaded. Lorvara cannot see where it came from, so it asks you. Tick I declare this image is AI-generated under the picture, once per picture, and it registers. The declaration is recorded with your account and the date, and the registration says it rests on your word rather than on Lorvara’s records.

This is Lorvara’s rule, not the vendor’s. Our model aggregator’s asset library does not ask where an image came from. Lorvara asks, because registering a face turns off the check that would otherwise stand between it and a video model.

Either way, every picture still goes through the same checks before it is sent: the age check below, the limit per character, and the aggregator’s own review. A declaration opens the door to registering. It does not skip any of them.

Deleting the source from your library does not undo a proven picture. When you add a generated image to a card, Lorvara records its history then and there. Delete the original generation later and that record still stands, so the image stays eligible.

A reference that was on a card before this existed has no record of where it came from, so it takes the declared route: tick the box under it. If Lorvara did generate it, putting it back through Use a generated image records that, and it registers as proven instead. The same applies to a picture added before 3 October 2026 whose source you have since deleted.

A character that reads as under 18 is never registered

Two independent signals, and either one refuses, and so does not being sure:

The character’s own words: the name, the description and the state names, as they are written on the card. “Emmy (Child)”, “aged nine”, “a teenager”.
An age check on the image itself. It answers adult, minor, or cannot tell. Only adult passes; cannot tell refuses, and so does a check that could not run.

There is no override anywhere in the product. Said plainly: a legitimate photoreal child character (a family film, a school story) cannot use Seedance with its face through Lorvara. It still works on Kling O1, which takes photoreal faces directly, and it works on Seedance as a stylized character.

This is deliberate, and it is not symmetrical on purpose. A character wrongly refused loses one route and keeps the others. A character wrongly allowed is a photoreal child in a third party’s storage with the face check turned off.

Removing, regenerating and deleting

There is one case in which Lorvara deletes a registration: a picture leaving a character that is still in your brief. Remove the picture, or replace it, and Lorvara asks our model aggregator to delete the registered copy the next time that character’s images are registered or used in a generation. A deletion at the aggregator is permanent. Nothing of yours is lost: the picture stays in Lorvara, and re-registering it takes seconds.

Regenerating a sheet and putting the new picture on the card retires the old registration and registers the new one, so a stale picture is not sent.
If the aggregator does not confirm a deletion, Lorvara does not record it as deleted, and asks again the next time.
A character used in another project registers its own copies there. The registration belongs to the picture under the brief that holds it, so removing one project’s reference never disturbs another’s.

What does not delete a registration today. Removing a whole character from a brief, deleting a brief or a project, and closing your account all leave the registered copy with our model aggregator. To have registered images deleted, write to us from the address on your account and say which characters, or that you mean all of them. The privacy policy, section 9, says the same thing and gives the address.

While it is still registering

A generation that names a character whose registration has not finished is held, not failed: it keeps its place and its reservation, and it goes as soon as registration ends. If registration ends in failure, the generation fails with that reason and the credits come back. Nothing is charged for registering, ever.

Limits

64 images per character at our model aggregator. Past that, the next one is refused with a plain reason rather than something else being quietly evicted. A character holds at most six states of five views each, so its card alone does not reach it.
Registration is for the Seedance family only. Every other model takes references as pictures, exactly as before.