How to use
- Pick bars-32x16.png and then tile-48.png.
- Leave the direction on horizontal for an 80 by 48 PNG.
- Switch to vertical for a 48 by 64 PNG.
Formula / how it works
bars-32x16.png is 32 by 16. tile-48.png is 48 by 48. Side by side, the PNG is 80 by 48. The first image is in the top left, so pixel 0,0 is the red of the left half of the bars, about 220, 30, 30. The second image starts at x 32. Under the 16-pixel-tall bars, the rest of the 48-pixel height is white. That white is the gap the page warns about. It is not a crop and not a blend.
Stacked, the PNG is 48 by 64. The bars sit on top, the tile sits under them, and the width is the wider of the two. The bars are narrower, so a white column sits beside them. The second file is not scaled to match the first. Scaling would be a guess. If you need the same height first, use the resizer, then come back.
Only two files are read. A third file in the picker is ignored. GIF files contribute the frame the browser decodes, which is the first. The output is always PNG, so the white gap is real pixels, not a missing background in a JPEG. You can turn that PNG into a JPEG on the PNG to JPG page if a form demands JPEG, and the white will stay white.
The direction control is the word horizontal or vertical. The default is horizontal. The check for the stacked run sets vertical and expects 48 by 64. Those two sizes are the whole test: addition of widths, or addition of heights, and the max of the other side.
This is the "two photos on one page" job as a picture, not as a PDF page. If you need each photo on its own PDF page, use JPG to PDF or images to PDF. If you need them on one PDF page with margins, this PNG can be embedded later, but this page will not invent an A4 frame. The white gap is only the rectangle of the canvas.
The horizontal canvas is 80 pixels wide because 32 plus 48 is 80, and 48 pixels tall because the tile is taller than the bars. The vertical canvas is 48 wide and 64 tall. Pixel 0,0 stays the red of the bars in the side-by-side file. The white gap is painted, not transparent.
Make each photo its own page with JPG to PDF. Flatten the PNG with PNG to JPG if you need JPEG.
Worked examples
Bars beside the tile
Inputs: cim-f: bars-32x16.png, tile-48.png | cim-dir: horizontal
On this page, take bars-32x16.png, tile-48.png, then horizontal and press Combine. Look for the white gap beside the shorter image.
Result: Combined 2 images horizontal: 80×48 PNG. The second file sits on the right. Different heights le…
Bars under the tile
Inputs: cim-f: bars-32x16.png, tile-48.png | cim-dir: vertical
On this page, take bars-32x16.png, tile-48.png, then vertical and press Combine. Look for the white gap beside the shorter image.
Result: Combined 2 images vertical: 48×64 PNG. The second file sits under the first. Different heights l…
Use cases
- Putting the red bars to the left of the 48-pixel tile.
- Leaving a white gap under the 16-pixel bars when the tile is taller.
- Stacking the bars on top of the tile without scaling either one.
- Ignoring a third file if the picker offered one.
Tips & limitations
- Pixel 0,0 on the side-by-side file is the red of the bars, near 220, 30, 30.
- The tile starts at x 32 in the horizontal file.
- Neither image is stretched to match the other.
- The download is PNG, so the white gap is real pixels.
FAQ
Why is the side-by-side file 80 by 48?
32 plus 48 is 80. The height is the taller tile, 48. The bars do not grow.
Why is the stack 48 by 64?
The width is the wider tile, 48. The heights add: 16 plus 48 is 64.
What colour is the gap?
White. It fills the rectangle beside or under the shorter image.
Are the photos scaled?
No. Match the sizes on the resizer first if you need that.
How many files are read?
Two. A third selection is ignored.
Is a GIF animation kept?
No. The frame the browser decodes, usually the first, is the one that is drawn.
80 by 48 and 48 by 64 describe bars-32x16.png with tile-48.png. Other pairs add differently.