Copying and pasting can change the image representation used by the receiving application, sometimes flattening transparency onto white. First determine whether the white is only a display background or actual opaque pixels. Import the original transparent file directly and compare it with the pasted version before editing the artwork itself.
Check the source on contrasting backgrounds
Open the original file in an editor that can display alpha and place it over a dark temporary layer. If the subject has a transparent surround there, the original is usable. A white editor canvas alone does not show whether alpha exists; neither does a checkerboard unless you know it is the application's preview.
Save a copy in a suitable alpha-supporting format and reopen it. W3C's PNG specification defines image transparency, while its Clipboard API specification addresses clipboard data types. Those standards do not guarantee that every native application transfers or imports the same transparent representation.
Compare three transfer routes
- Import the original file using the destination's image-placement command.
- Paste the copied image into a document that supports transparency.
- Place both versions over the same dark background and inspect their edges.
If direct import preserves transparency but paste creates an opaque rectangle, the transfer route is the likely problem. If both are opaque, investigate the source export or destination document mode. If both remain transparent but look white only in one preview, the preview background may explain the appearance.
A hypothetical logo handoff
Imagine a creator delivering an original illustrated logo as a transparent PNG. Pasting it into a slide makes a white rectangle, while inserting the file into a supported layout preserves the cutout. The creator sends the file with brief placement instructions instead of repainting the logo's background.
This is a hypothetical comparison. The exact behavior depends on the applications involved. The important evidence is which route changes the result when the same original and background are used.
Avoid destructive fixes to a transfer problem
Do not erase every white pixel indiscriminately. The logo may contain white lettering or highlights that belong to the design. If the original still has alpha, return to it and use a transfer method that retains it. Keep an editable source as well as the delivery image.
In Imagild, verify transparency in the actual downloaded file rather than inferring it from the creation preview. A screenshot of a transparent preview is usually a new rectangular screenshot, not the original alpha-bearing asset.
Acceptance at the destination
Inspect the imported delivery over at least two contrasting backgrounds. Require intact internal white details, no opaque surround and no new edge halo. If the destination needs a solid background, create that version deliberately and name it separately. A white-background export can be useful; it should not be confused with a transparent version that failed during copying.