Emitting Artifactsv4.0.176

Sometimes you wish to generate additional files when rendering your video. For example:

• A .srt subtitle file
• A .txt containing chapters of the video
• A CREDITS file for the assets used in the video
• Debug information from the render.

You can use the <Artifact> component to emit arbitrary files from your video.

note

Emitting artifacts is not currently supported by @remotion/cloudrun.

Example

import React from 'react';
import {Artifact, useCurrentFrame} from 'remotion';
import {generateSubtitles} from './subtitles';

export const MyComp: React.FC = () => {
  const frame = useCurrentFrame();
  return <>{frame === 0 ? <Artifact filename="captions.srt" content={generateSubtitles()} /> : null}</>;
};

Rules of artifacts

1

The asset should only be rendered for one single frame of the video. Otherwise, the asset will get emitted multiple times.

2

It is possible to emit multiple assets, but they may not have the same filename.

3

For the content prop it is possible to pass a string, or a Uint8Array for binary data. Passing an Uint8Array should not be considered faster due to it having to be serialized.

Emitting thumbnailsv4.0.290

You can emit the image data of the current frame as an artifact.

import {Artifact, useCurrentFrame} from 'remotion';

export const MyComp: React.FC = () => {
  const frame = useCurrentFrame();
  return <>{frame === 0 ? <Artifact content={Artifact.Thumbnail} filename="thumbnail.jpeg" /> : null}</>;
};

1

The content prop should be set to Artifact.Thumbnail.

2

The imageFormat setting determines the format of the image. The extension you pass is meaningless.

3

The other rules of artifacts still apply.

Receiving artifacts

In the CLI or Studio

Artifacts get saved to out/[composition-id]/[filename] when rendering a video.

Using renderMedia(), renderStill() or renderFrames()

Use the onArtifact callback to receive the artifacts.

import {renderMedia, OnArtifact} from '@remotion/renderer';

const onArtifact: OnArtifact = (artifact) => {
  console.log(artifact.filename); // string
  console.log(artifact.content); // string | Uint8Array
  console.log(artifact.frame); // number, frame in the composition which emitted this

  // Example action: Write the artifact to disk
  fs.writeFileSync(artifact.filename, artifact.content);
};

await renderMedia({
  composition,
  serveUrl,
  onArtifact,
  codec: 'h264',
  inputProps,
});

Using renderMediaOnWeb() or renderStillOnWeb()

Use the onArtifact callback to receive artifacts when rendering using renderMediaOnWeb().

const MyComp: React.FC = () => {
  const frame = useCurrentFrame();
  return <>{frame === 0 && <Artifact filename="metadata.json" content={JSON.stringify({title: 'My Video'})} />}</>;
};

const artifacts: EmittedArtifact[] = [];

await renderMediaOnWeb({
  composition: {
    ...composition,
    component: MyComp,
  },
  onArtifact: (artifact) => {
    console.log(artifact.filename); // string
    console.log(artifact.content); // string | Uint8Array
    console.log(artifact.frame); // number
    artifacts.push(artifact);
  },
});

The same callback is available for renderStillOnWeb():

const MyComp: React.FC = () => {
  return <Artifact filename="thumbnail.png" content={Artifact.Thumbnail} />;
};

const artifacts: EmittedArtifact[] = [];

await renderStillOnWeb({
  composition: {
    ...composition,
    component: MyComp,
  },
  frame: 0,
  imageFormat: 'png',
  onArtifact: (artifact) => {
    artifacts.push(artifact);
  },
});

Using the Remotion Lambda CLI

When using npx remotion lambda render or npx remotion lambda still, artifacts get saved to the S3 bucket under the key renders/[render-id]/artifacts/[filename].

They will get logged to the console and you can click them to download them.
The --privacy option also applies to artifacts.

Using renderMediaOnLambda()

When using renderMediaOnLambda(), artifacts get saved to the S3 bucket under the key renders/[render-id]/artifacts/[filename].

You can obtain a list of currently received assets from getRenderProgress().

import {getRenderProgress} from '@remotion/lambda/client';

const renderProgress = await getRenderProgress({
  renderId: 'hi',
  functionName: 'hi',
  bucketName: 'hi',
  region: 'eu-central-1',
});

for (const artifact of renderProgress.artifacts) {
  console.log(artifact.filename); // "hello-world.txt"
  console.log(artifact.sizeInBytes); // 12
  console.log(artifact.s3Url); // "https://s3.eu-central-1.amazonaws.com/remotion-lambda-abcdef/renders/abcdef/artifacts/hello-world.txt"
  console.log(artifact.s3Key); // "renders/abcdef/artifacts/hello-world.txt"
}

Using renderStillOnLambda()

When using renderStillOnLambda(), artifacts get saved to the S3 bucket under the key renders/[render-id]/artifacts/[filename].

You can obtain a list of received assets from artifacts field of renderStillOnLambda().

import {renderStillOnLambda} from '@remotion/lambda/client';

const stillResponse = await renderStillOnLambda({
  functionName,
  region,
  serveUrl,
  composition,
  inputProps,
  imageFormat,
  privacy,
});

for (const artifact of stillResponse.artifacts) {
  console.log(artifact.filename); // "hello-world.txt"
  console.log(artifact.sizeInBytes); // 12
  console.log(artifact.s3Url); // "https://s3.eu-central-1.amazonaws.com/remotion-lambda-abcdef/renders/abcdef/artifacts/hello-world.txt"
  console.log(artifact.s3Key); // "renders/abcdef/artifacts/hello-world.txt"
}

Using Cloud Run

In the Cloud Run Alpha, emitting artifacts is not supported and will throw an error.
We plan on revising Cloud Run to use the same runtime as Lambda in the future and will bring this feature along.

See also

• <Artifact>