← All Fusion workflows
Basic workflowMediaInBackgroundMergePNGFormat

Fit an Image to the Project Frame in Fusion

This workflow solves a common Fusion issue: a source graphic can have its own resolution, for example 1024×1024, while the composition is 3840×2160. Used directly, the image keeps its original canvas. The fix is to create a transparent Background at the project resolution and connect the image to the Merge Foreground. From that point on, the chain receives a full-size project frame while preserving the PNG alpha.

Final result: Fit an Image to the Project Frame in Fusion

Why this graph is built this way

Workflow logic

The setup is intentionally minimal. Background defines frame dimensions and transparency; Merge places the PNG or logo inside that frame. This is more predictable than blindly scaling MediaIn because the canvas size is controlled by a dedicated node. It is especially useful before Transform, Glow, Blur, particles, masks or export operations that depend on correct frame dimensions.

Node tree

Connection diagram

The cable colors follow Fusion conventions: blue is an Effect Mask, neutral lines carry images, and colored ports indicate specific node inputs. Node-page links are intentionally disabled on the English diagram until the matching Fusion Encyclopedia pages are translated.

Node order

How to read the chain

1

Logo → Merge1

Connect the source PNG to Merge Foreground. This is the object that needs to live inside the project frame: a logo, icon, render or other alpha graphic.

2

Background6 → Merge1

Background6 creates a transparent frame at the required dimensions. In this example it is 3840×2160 with Alpha 0, so it defines canvas size without adding a visible background.

3

Merge1 → downstream nodes

After Merge, the image already has the project frame size and can be transformed, animated, blurred, masked or sent to MediaOut without the small-source-canvas problem.

Result

What the shot looks like

The PNG remains transparent but now lives inside a full 3840×2160 frame. It can be safely animated, composited, blurred, glowed or passed to MediaOut without downstream nodes unexpectedly operating on the original small canvas.

When to use it

Where it works

  • When a PNG, logo or icon is smaller than an HD, 2K or 4K project frame.
  • Before Glow, Blur, Transform, Merge, masks or particles that should operate at full-frame resolution.
  • Preparing alpha graphics for animation in Fusion.
  • Keeping transparency while matching the image to timeline dimensions.
  • Templates, intros, logos and overlays that must live inside a common project canvas.

Node parameters

What changes from the defaults

Background6

Background is used as a transparent project-size container rather than a visible color fill.

  • Width: 3840
  • Height: 2160
  • UseFrameFormatSettings: enabled
  • TopLeftAlpha: 0
  • GlobalOut: 239

Merge1

Merge combines the transparent project frame and PNG. Background goes to the yellow Background input; Logo goes to the green Foreground input. Size can be adjusted without modifying the original media.

  • Background: Background6.Output
  • Foreground: Logo.Output
  • Size: 1.06818181818182
  • PerformDepthMerge: 0

Logo

Logo is a project PNG resource rather than a universal Fusion node, so the diagram treats it as a static asset rather than an encyclopedia link.

  • Source: PNG from MediaPool
  • Original format: 1024×1024
  • Loop: enabled
  • Alpha preserved

Common mistakes

What not to break

  • Do not feed a small PNG deep into a graph if later effects need a full project-size frame.
  • Do not make Background opaque when it is meant to act only as a transparent container; use Alpha 0.
  • Do not swap Merge inputs: the transparent frame is Background and the graphic is Foreground.
  • Do not rely on Transform alone to solve the canvas problem. Transform changes scale and position but does not define a new full-frame canvas by itself.
  • Do not treat a project-specific MediaIn asset as an encyclopedia node link.