Portable Network Graphics (.png)

W3C Estándar

Portable Network Graphics (PNG) is an unencumbered raster graphics file format that supports lossless data compression, indexed colors, and variable alpha channel transparency.

Convertir de PNG a JPG

Convertidor gratuito de PNG a JPG en el navegador. Convierte archivos al instante en tu dispositivo.

Comprimir PNG en línea

Compresión 100% privada en el navegador – los archivos nunca salen de tu dispositivo

Inspeccionar y metadatos

Los sistemas operativos y analizadores de archivos identifican los archivos de PNG inspeccionando la secuencia de bytes binarios inicial:

Selecciona o arrastra archivos

Selecciona o arrastra archivos aquí

Conversión 100% privada en el navegador; los archivos nunca salen de tu dispositivo

o pega Ctrl+V
Garantía de privacidad sin transmisión de red: 0 bytes subidos a servidores externos. Todo el procesamiento se realizó de forma local en el entorno seguro de tu navegador.

Firma de cabecera a nivel de bytes (Bytes mágicos)

Los sistemas operativos y analizadores de archivos identifican los archivos de PNG inspeccionando la secuencia de bytes binarios inicial:

FIRMA HEXADECIMAL (DESPLAZAMIENTO 0):

89 50 4E 47 0D 0A 1A 0A

REPRESENTACIÓN ASCII: .PNG....

Estandarización: W3C Recommendation (1996) / ISO/IEC 15948:2004

Especificaciones técnicas

Arquitectura del contenedorChunk-based binary container with 4-byte CRC32 verification per chunk
CompresiónDeflate (LZ77 + Huffman coding) with 5 predictive scanline filters (None, Sub, Up, Average, Paeth)
Orden de bytes (Endianness)Big-Endian (network byte order) for chunk lengths, dimensions, and CRCs
Espacios de colorsRGB, Display P3, Indexed Palette (1-8 bit), Grayscale, Truecolor (24/48-bit)
Canales y estructuraRGB + Alpha (Up to 16 bits per channel / 64-bit RGBA)
Dimensiones máximas2,147,483,647 x 2,147,483,647 pixels (4-byte unsigned integers)
TransparenciaFull 8-bit / 16-bit variable alpha transparency channel
Streaming y progresivoAdam7 7-pass interlacing algorithm enables progressive 2D scanline rendering

Matriz de comparación técnica: PNG frente a la competencia

Atributo técnicoPNG (Actual)WebPAVIFJPEG
Compression TypeStrictly lossless (Deflate + 2D predictive filters)Lossy (VP8) & Lossless (VP8L)Lossy (AV1 intra) & LosslessStrictly lossy (Discrete Cosine Transform)
Alpha TransparencyFull 8-bit / 16-bit variable alpha channel8-bit alpha channel supported8-bit / 10-bit / 12-bit alpha supportedNo transparency channel support
File Size (Photographs)Large (typically 3x to 6x larger than lossy formats)Small (25%-35% smaller than JPEG)Ultra-small (40%-55% smaller than JPEG)Medium baseline
File Size (Graphics/UI)Extremely compact for screenshots, line art, and textExcellent lossless modeGood, but slower to encodePoor (produces ringing artifacts along sharp edges)
Browser Compatibility100% universal across all browsers since 199897%+ modern browser support93%+ modern browser support100% universal

Modos de corrupción comunes y guía de recuperación hexadecimal

⚠️ Image viewer displays 'Fatal error: Not a valid PNG file' or fails to open.

Causa raíz: The first 8 bytes were altered by an ASCII transfer mode (mangling 0x0D 0x0A into 0x0A or 0x0D 0x0D 0x0A).

Recuperación: Open the file in a hex editor and verify the first 8 bytes match '89 50 4E 47 0D 0A 1A 0A'. Restoring these exact 8 header bytes frequently recovers the image.

⚠️ pngcheck reports 'CRC error in chunk IDAT' or image loads partially with corrupt bottom scanlines.

Causa raíz: Bit corruption in the compressed zlib datastream or invalid CRC32 checksum in an IDAT chunk.

Recuperación: Use pngcheck -f or Deflate stream recovery utilities to recalculate valid CRC32 values, or decompress surviving scanlines up to the corrupt block.

⚠️ Image renders fine in desktop viewers but fails in iOS applications.

Causa raíz: iOS expects Apple's proprietary CgBI byte swapped format, or non-standard color space chunks.

Recuperación: Normalize the image using 'pngcrush -revert-iphone-optimizations' to restore standard W3C RGBA ordering.

Análisis de seguridad y vectores de ataque al analizador

PNG is widely parsed across all platforms. Modern security concerns center on parser memory exhaustion and ancillary chunk injection.

Vectores de ataque conocidos

  • Oversized tEXt and zTXt metadata chunks triggering Out-Of-Memory (OOM) denial-of-service in un-sandboxed decoders.
  • Heap buffer overflow vulnerabilities in legacy libpng releases (e.g. CVE-2015-8126 in png_set_PLTE).
  • Pixel flood decompression attacks where an image with small file size declares enormous dimensions (e.g. 100,000 x 100,000 pixels).
  • Steganographic exfiltration hiding encrypted payloads in ancillary private chunks (e.g. eXIf or custom chunk types).

Mejores prácticas defensivas: Always validate image dimensions before allocating pixel buffers in memory. Strip non-essential ancillary chunks (eXIf, tEXt) on user uploads using a memory-safe sanitizer.

Orígenes históricos e hitos

2004Standardized internationally as ISO/IEC 15948.
1996PNG 1.0 published as a W3C Recommendation.
1995Created on Usenet comp.graphics as an open replacement for GIF following Unisys's LZW patent fee enforcement.

Ventajas clave y pros

  • Lossless compression guarantees zero pixel degradation or generation loss upon saving.
  • Smooth 8-bit alpha transparency enables clean blending on complex backgrounds.
  • Gamma correction and chromaticity chunks ensure consistent rendering across diverse monitors.

Limitaciones técnicas y contras

  • Significantly larger file sizes compared to modern lossy formats like WebP or AVIF for photographic content.
  • No native multi-frame animation in standard PNG (requires APNG extension).
  • High bit-depth (16-bit per channel) creates huge uncompressed in-memory decode buffers.

Curiosidades técnicas interesantes

  • The 8-byte magic header was specifically designed to detect CR/LF line ending corruption by FTP transfers.
  • The unofficial recursive acronym for PNG was 'PNG's Not GIF'.
  • Apple uses a proprietary CgBI chunk in iOS app PNGs that reverses RGBA to BGRA for direct GPU rendering.

Preguntas técnicas frecuentes

Why does a PNG file size sometimes increase when saved in image editors?

Different software suites use varying Deflate compression levels and predictive scanline filter heuristics. Programs like Photoshop frequently append uncompressed color profiles, XMP metadata blocks, and unoptimized IDAT chunk sizes. Dedicated tools like File2File Compressor re-evaluate all 5 scanline filters to achieve minimal file size.

What is the difference between PNG-8 and PNG-24?

PNG-8 uses an indexed color palette of up to 256 colors (similar to GIF), producing very small files suitable for simple icons. PNG-24 supports 16.7 million colors (Truecolor 8 bits per channel), with PNG-32 adding an 8-bit alpha transparency channel.

Why does PNG have 5 predictive scanline filters?

Deflate compresses repeated byte patterns. Because photographic or gradient pixel values change gradually, PNG filters each scanline (None, Sub, Up, Average, Paeth) by calculating differences between adjacent pixels. This transforms gradient data into strings of near-zero bytes that compress dramatically better under Deflate.

Does PNG support CMYK color spaces for commercial printing?

No. The official W3C PNG specification deliberately restricts color types to Grayscale, Indexed, and RGB. Professional print workflows requiring CMYK must use TIFF or PDF containers.