Why Your PDF Signature Has a White Box—and How to Fix It
A white rectangle behind a placed signature usually belongs to the image you uploaded, not to the PDF page. If the source image has opaque white pixels, placing it over a form line places those pixels over the line too; merely changing the filename to .png does not remove them.
First check the image against a dark or colored background, then make its background genuinely transparent and save it as a PNG before signing again. Sign PDF can preserve a transparent PNG, but it does not erase the background of a photograph or a JPEG for you.
Diagnose the box before editing anything
Save an untouched copy of the PDF and the signature image, then compare three views: the image on its own, the signature preview in the tool, and the exported PDF. That sequence tells you whether the rectangle came from the source pixels, appeared during placement, or appeared only after another application processed the output.
| What you see | Most useful check | Likely next step |
|---|---|---|
| White rectangle in the source image and exported PDF | Show the image over a dark background | Remove the image background and export a transparent PNG |
| PNG filename, but still a white rectangle | Inspect whether its white pixels are opaque | Change the pixels; renaming or converting the file is insufficient |
| Preview looks clean, but a later copy has a box | Compare the first exported PDF with the later copy | Identify the application or conversion step that changed it |
| Box only in one reader | Open the same saved PDF in another capable reader | Check viewer rendering before rebuilding the file |
| No box, but the mark hides text | Check position and size against the original form | Move or resize the signature on an unsigned copy |
Do not treat a white page as a meaningful transparency test, because opaque white and transparent pixels can look identical on white. Put the image over dark gray, blue, or a checkerboard in an image editor, and inspect the entire rectangle around the ink rather than just the signature strokes.
If the rectangle appears only after you print, flatten, or re-export the signed PDF elsewhere, keep the first downloaded file for comparison. A later workflow can alter an image’s appearance, and the correct repair depends on which file first shows the problem.
Why PNG and JPEG behave differently
The extension describes a file format, not the actual color of its background. The W3C PNG specification allows an optional alpha channel for transparency, which means one PNG can have transparent surrounding pixels while another PNG is completely opaque.
JPEG does not provide an alpha channel, as the MDN image-format guide explains. A JPEG photograph of ink on paper therefore carries the paper color as picture data, even when the sheet looked perfectly white under the camera.
| Source image | Can the surrounding area be transparent? | What an export should be expected to show |
|---|---|---|
| Transparent PNG | Yes, if alpha data is actually present | PDF content beneath the transparent area remains visible |
| Opaque PNG | The format can, but this particular image does not | The stored white or gray background remains visible |
| JPEG photograph | No alpha channel in the source | The photographed paper and shadows remain part of the mark |
| Drawn or typed mark made on a clear canvas | Yes, when the application exports transparency | The mark without a rectangular paper background |
Saving a JPEG as PNG preserves the same visible pixels unless you also remove the background. Likewise, cropping the image tightly reduces the size of the rectangle but leaves a smaller opaque rectangle; it is useful for placement, not for creating transparency.
This distinction matters most on a colored form, a shaded signature area, or a line that passes behind your name. On a plain white page, an opaque white image can appear acceptable until someone prints the file on a differently colored template or the mark overlaps a rule.
What this site’s Sign tool actually does
The upload control accepts valid PNG and JPEG images, checks the image data, and places a visible signature image on the selected PDF page. A PNG is retained with its existing transparency; a JPEG is decoded and converted to PNG for the export pipeline, but that conversion does not invent transparent pixels or remove its photographed background.
We checked both formats in the site’s browser regression test: the preview retained the source pixels, both uploaded images exported as valid placed images, and the transparent PNG produced a PDF image with a soft mask. The test also rejected malformed image bytes, so changing an arbitrary file’s extension to .png is not a useful workaround.
The Draw and Type options create a mark on an unfilled canvas and export it as PNG, avoiding a photographed paper background. They are useful when an image editor is unavailable, though a typed or mouse-drawn mark may not match handwriting you must reproduce.
The interface does not offer a background-removal control, and it does not place a certificate-based digital signature. The general signing guide covers placing and exporting a visible mark, while electronic signature versus digital signature explains the separate verification requirement.
Make a truly transparent signature image
Start with a clean photograph or scan of your handwritten signature on a bright, evenly lit sheet. Avoid shadows, folds, colored paper, and a pen whose ink is too pale to separate confidently from the background; each makes the boundary around the ink harder to isolate.
Open a copy of the image in an editor that can show and export transparency. Remove the paper background, inspect the edges over both a light and a dark test color, and correct any gray halo or accidentally erased parts of the letters before exporting.
Adobe’s background-removal instructions describe isolating a subject onto transparency and refining the mask when the automatic result is imperfect. The particular editor is less important than the result: the area outside the ink must be transparent, not painted white.
- Keep the original photo or scan so you can start again if the edges are damaged.
- Remove the surrounding paper in an editor with a transparency view.
- Inspect both dark and light backgrounds for white fringes and missing ink.
- Trim excess empty space without cutting off strokes or initials.
- Export as PNG with transparency enabled, then reopen that PNG for a second check.
A checkerboard shown in an editor is a useful clue, but confirm the exported file itself rather than relying on the unsaved editing canvas. Some export choices flatten layers onto white, so a transparent project can still become an opaque file at the last step.
If a background-removal service would require uploading a sensitive signature image, consider a local image editor or use the site’s Draw or Type option instead. The PDF processing here is local, as described in how browser-based PDF processing protects privacy, but a separate image service has its own data handling.
Place the corrected image and test the result
Open an unsigned original in Sign PDF, choose Upload image, and select the corrected PNG. Check the preview, set a modest width and height, place the mark on the intended page, export, and reopen the downloaded PDF rather than assuming the preview represents the final file.
Test the signature over a line or colored area if your real form contains one, because that is where an opaque rectangle becomes obvious. The preview may show the image correctly while placement, scale, or a later export changes the result, so inspect the actual file you intend to send.
| Final-file check | Why it matters |
|---|---|
| Open the downloaded PDF again | Confirms the saved file, not only the upload preview |
| Inspect the mark at normal and high zoom | Finds white halos, missing strokes, and pixelated edges |
| Look where the form line meets the image | Reveals an opaque rectangle that white paper can hide |
| Verify page, size, and date fields | Prevents a clean image from being placed on the wrong page or line |
| Compare in a second viewer if the result differs | Separates file data from a reader-specific display issue |
If the signature blocks nearby text, fix its dimensions or position before exporting another copy. A transparent background allows content to show through empty pixels, but dark ink still covers whatever lies directly beneath it.
For a date or printed name next to the mark, use Add Text to PDF rather than building those details into the signature photograph. The add-text guide explains how the site’s overlay behaves and why editing an existing line of PDF text is a different task.
When transparency is not the issue
If a correctly transparent PNG looks good in the first exported file but bad only after another PDF editor, printer workflow, or recipient app touches it, isolate that later step. Send yourself the original export, compare file sizes and page appearance, and ask the recipient to open the same bytes in another capable reader before changing a source image that was already sound.
A white box can also be an intentional field background supplied by the underlying form rather than by the signature image. Check the unsigned original at the same zoom and location; if the rectangle is present before signing, editing the signature cannot remove it.
Do not rebuild a certificate-signed document merely to improve the look of a visible mark, because page reconstruction can invalidate cryptographic verification. If the recipient requires a certificate-based signature, use a signing workflow built for that requirement and confirm the final validation status rather than substituting an image.
The practical rule is to repair the earliest artifact that contains the box. If the source image is opaque, make a genuinely transparent PNG or draw the mark anew; if only a later PDF copy develops the box, investigate that conversion while retaining the clean original export.