Format Atlas

Choose file formats with confidence

Browse categories and find practical format guidance.

Find a format by nameCompare two optionsChoose by purposeLook up a term

Browse by category

Start with the category that best matches your needs.

ArchiveA category of file formats covered by Format Atlas.Browse category AudioA category of file formats covered by Format Atlas.Browse category CAD and drawingsA category of file formats covered by Format Atlas.Browse category DataA category of file formats covered by Format Atlas.Browse category DocumentsA category of file formats covered by Format Atlas.Browse category EmailA category of file formats covered by Format Atlas.Browse category FontsA category of file formats covered by Format Atlas.Browse category ImagesA category of file formats covered by Format Atlas.Browse category Certificates and keysA category of file formats covered by Format Atlas.Browse category SpreadsheetsA category of file formats covered by Format Atlas.Browse category SubtitlesA category of file formats covered by Format Atlas.Browse category 3DA category of file formats covered by Format Atlas.Browse category VideoA category of file formats covered by Format Atlas.Browse category WebA category of file formats covered by Format Atlas.Browse category

Find a format

Check the purpose and features of each format before opening its details.

Open the filterable format list →

Expand all formats on this page (189)
AAC.aacAAC is a lossy audio codec standardized by MPEG. It may appear as a .aac file or an audio track inside a container; the codec is not the container.AI.aiAI is Adobe Illustrator's editing format. It can hold vector artwork, but its delivery role differs from SVG and PDF; choose an output format based on the recipient and final use.AIFF.aiff · .aifAIFF is an Apple-defined audio file format often used for uncompressed PCM. Its role resembles WAV in production, but structure and tool support differ; AIFF-C variants also exist.AMR.amrAMR is a speech-oriented audio codec found in call recordings and older mobile files. It is not designed as a general high-fidelity music format.APNG.apng · .pngAPNG extends PNG so that one image file can contain animation. Its lossless compression and transparency can suit short interface animations and diagrams. Compare support, color and transparency needs, and output size when choosing between APNG, GIF, and WebP.Apache Arrow IPC.arrow · .feather · .arrowsApache Arrow provides a columnar data format and libraries; Arrow IPC serializes that data for exchange between processes and applications. The file format commonly uses .arrow and supports random access to record batches through its footer. The stream format commonly uses .arrows and delivers messages in sequence. Feather V2 is a name for files based on the Arrow IPC file format.Aseprite.ase · .asepriteAseprite's `.ase` and `.aseprite` files are binary project formats for pixel art and 2D sprites. They preserve more than the image: layers, color mode, palette, animation frames, and frame durations can remain editable. For a game or website, export to PNG, GIF, a sprite sheet, or another format required by the destination.AVI.aviAVI is a RIFF-based container for audio and video streams. The .avi extension does not identify the internal codecs, so playback and file size vary by content.AVIF.avifAVIF is a still-image format based on the AV1 Image File Format specification. It is an option for balancing image size and quality in web delivery, rather than an automatic replacement for JPEG or WebP.Avro.avroApache Avro serializes records according to a schema that can be expressed in JSON. Its types include records, arrays, maps, and unions; readers and writers need compatible schemas.BAM.bamBAM (Binary Alignment/Map) is the binary representation of SAM alignment data defined by the SAMv1 specification. BAM is normally compressed in BGZF blocks; this block structure supports indexed access to regions. It can store reference headers, read names, FLAG, CIGAR, positions, sequence qualities, and tags, and may include unmapped reads. Coordinate-sorted BAM can be paired with an index such as BAI or CSI. BAM is suited to machine processing, but not direct reading; reference identity and index consistency matter.BED.bedBED is text listing chromosome, start and end. Starts are zero-based and the end is excluded. It does not store sequence itself or per-base quality.bedGraph.bedGraphbedGraph is text with chromosome, start, end and numeric value. Coordinates are zero-based and end-exclusive. Intervals may carry positive or negative integer or real values.bigBed.bb · .bigBedbigBed is an indexed binary format made from BED-type data. Compatible browsers can read selected regions. It is not simply a gzip-compressed BED file.bigWig.bw · .bigWigbigWig is indexed binary storage for genomic values. It can be created from WIG or bedGraph; compatible tools access selected regions. Its data role differs from bigBed.Blender project.blendA .blend file is Blender's native project format. It stores Blender scene data such as objects, meshes, materials, and animation for continued editing. Unlike an interchange format, it may not reproduce the same project in other applications, and external dependencies such as textures may need to be managed separately.BMP.bmpBMP is a raster image format historically used mainly on Windows. It is often stored without compression and can become large, so new web images usually use PNG or WebP instead.Brotli.brBrotli (.br) is a lossless compressed data format using LZ77-family references and Huffman coding. It is also used as the HTTP content-coding token br; servers may deliver precompressed files when the client supports it. The stream is not an archive and does not necessarily include metadata such as the original size or a checksum.BSON.bsonBSON (Binary JSON) is a binary serialization format for documents with a JSON-like structure. It also supports types that standard JSON does not, including dates, binary data, and ObjectId. MongoDB uses it widely, but BSON is not ordinary JSON text and requires a BSON-aware driver or tool.BUFR.bufr · .bufBUFR (Binary Universal Form for the Representation of meteorological data; WMO FM 94) is a binary format for encoding and exchanging observations with table-driven descriptors. Messages contain sections for identification, data description, and data; descriptor sequences define how values are represented and interpreted. Check the edition and master or local tables.BZIP2.bz2 · .bzBZIP2 compresses data losslessly. A .bz2 file usually compresses one data stream; tar.bz2 combines tar archiving with BZIP2 compression.CBOR.cborCBOR (Concise Binary Object Representation) is an IETF standard for encoding data items such as numbers, strings, arrays, and maps in binary. It is designed to support compact implementations and messages while remaining extensible, and it can represent JSON-like data. It is not a text format, so reading and writing it requires a CBOR-aware tool or library.CRAM.cramCRAM stores sequencing reads and alignments using encodings that can exploit differences from a reference sequence, often achieving greater compression than BAM. The specification supports both lossless and lossy preservation strategies and does not prescribe which data must be retained. A .cram extension alone therefore cannot confirm whether base qualities or tags were preserved; check the creating tool and settings. Some files or workflows need an exact external reference to decode, while references can also be embedded. CRAI indexes support regional access.CRT.crt · .cerCRT and CER are extensions often used for X.509 certificates. The extension alone does not tell whether the file uses PEM text or DER binary encoding.CSR.csrA CSR contains a public key and requested identity information, signed using the corresponding private key. It is submitted to a certificate authority; it is not an issued certificate.CSS.cssCSS is a stylesheet language for document presentation. Selectors and declarations control how elements look, while HTML provides the page structure.CSV.csvCSV is a text format that represents tabular data with rows and delimiters. It suits simple table exchange but does not retain XLSX formulas, formatting, or multiple sheets.DAE.daeDAE files use COLLADA to describe 3D geometry, materials, animation, and other scene data in XML. Actual import and export support varies among tools.DDS.ddsDDS is a texture container used with Direct3D. It can store compressed textures, mipmaps, and cube maps, so it is common in game and 3D assets rather than ordinary web images.DER.derDER is a binary encoding of ASN.1 structures. A .der file may hold a certificate or another structure; identify its contents before use.DICOM.dcmDICOM is a standard for storing and exchanging medical images and related information. A Part 10 file, commonly named with the .dcm extension, contains file meta information followed by a data set representing one SOP Instance. It may include image pixels plus examination, equipment, or patient attributes. Pixel encoding and compression depend on the Transfer Syntax, so DICOM is more than an ordinary image file.Digital Negative.dngDNG (Digital Negative) is a publicly documented image format published by Adobe for storing camera raw information. Based on TIFF, it can hold unrendered camera data, metadata, and previews. It does not guarantee that every camera-specific feature or item of shooting information remains identical after conversion; check the raw-processing software and its handling of camera-specific data.DOC.docDOC is the legacy binary document format used by older Microsoft Word versions. For new editing, DOCX is usually preferred; use PDF for view-only distribution.DOCX.docxDOCX is the WordprocessingML document format in Office Open XML. It packages XML parts, images, styles, tables, and equations for document creation and editing.DWG.dwgDWG stores drawings with layers and annotations for AutoCAD-related workflows. File versions differ, so an older CAD application may not open a newer DWG.DXF.dxfDXF represents AutoCAD drawing data as group codes and values. It can exchange entities, layers, and text, but a recipient's tool and format version may interpret features differently.E57.e57E57 exchanges point data from 3D imaging systems. ASTM's public abstract says it can store 3D points, attributes such as color or intensity, and photographs obtained by a 3D imaging system; the file combines binary and XML data. It is not merely another LAS/LAZ extension because scan-related imagery can also be exchanged.EML.emlAn EML file saves an individual email message. It can include headers, message content, and attachments; display can differ between mail applications..env.envA .env file is a conventional text file for writing environment-variable names and values for compatible applications and development tools. There is no single universal specification: quoting, comments, variable expansion, and precedence over existing environment variables depend on the loader.EPS.epsEPS is an Encapsulated PostScript artwork exchange format used in print and production workflows. SVG, PDF, or PNG can be more appropriate for web delivery or general viewing.EPUB.epubEPUB is a digital publication format commonly used for ebooks. Reflowable EPUB content adapts text flow to the reader's screen and settings.OpenEXR.exrOpenEXR (.exr) is an HDR image format used in high-quality film, VFX, and CG workflows. It supports 16-bit half or 32-bit floating-point pixels, multiple channels, and several compression methods. It can preserve a wider range of luminance and color for production than ordinary display images, but the receiving software must support the file's features.FASTA.fasta · .faFASTA is a text format with a definition line starting with > followed by sequence data. This article covers nucleotide and reference sequences. FASTA alone contains no per-base quality scores.FASTQ.fastq · .fq · .fastq.gz · .fq.gzFASTQ is a widely used text format that pairs sequencer read sequences with per-base quality scores. A common record has an identifier beginning with `@`, a sequence, a `+` separator, and a quality string whose length matches the sequence. FASTQ has no single formal specification, and incompatible quality encodings exist, including Sanger Phred+33 and historical Solexa/Illumina variants. Files commonly use `.fastq` or `.fq` and may be externally compressed, for example with gzip. FASTQ usually stores reads before alignment; it does not serve the same role as SAM/BAM alignment records with reference positions.FBX.fbxFBX is used to exchange 3D models, materials, cameras, lights, rigs, and animation. Export settings and tool support vary, so imported scenes need inspection.FIT.fitFIT (.fit) is a binary format for storing and sharing data from sports, fitness, and health devices. It can contain messages for activities, sensor measurements, events, workouts, and courses. Which fields an app can read depends on the FIT profile and the receiving software; decoding may require the FIT SDK.FITS.fits · .fit · .ftsFITS (Flexible Image Transport System) is a standard used mainly in astronomy to store and exchange scientific data. It concatenates Header/Data Units (HDUs), each containing a header and data, so one file can hold image arrays, spectra, and ASCII or binary tables. Headers use 80-character cards, and HDU boundaries are padded to 2880-byte blocks.FLAC.flacFLAC restores the original PCM data after decoding. It is useful for storing audio at a smaller size than uncompressed PCM, but the actual size depends on the source.FlatGeobuf.fgbFlatGeobuf is a binary geographic feature format based on FlatBuffers. It contains a header, an optional spatial index and feature data. A .fgb file holds a single layer.FLV.flvFLV was used as a Flash Video container. For existing files, inspect both the video and audio codecs; modern browser playback should not be assumed from the .flv extension.GeoJSON.geojson · .jsonGeoJSON represents geographic features and geometry in JSON. Coordinates use longitude before latitude under the standard coordinate system.GeoPackage.gpkgGeoPackage (.gpkg) is an SQLite database file that stores geospatial data under the OGC GeoPackage standard. It can hold vector features, raster map tiles at multiple zoom levels, and non-spatial attributes in one file, including for offline and mobile use. An SQLite file is not automatically a GeoPackage: it must follow the standard's schema and requirements.GeoParquet.parquetGeoParquet adds geometry-column and geographic metadata conventions to Parquet. This article covers specification 1.1.0. A .parquet extension alone does not prove conformance.GeoTIFF.tif · .tiffGeoTIFF specifies how geographic reference information is stored in TIFF imagery. Reserved tags describe how raster pixels map to geographic or projected coordinates and may identify a coordinate reference system. Image and compression choices vary as in TIFF; the extension alone cannot confirm georeferencing.GFF3.gff3 · .gffGFF3 is an annotation format with nine tab-separated columns. Start and end are one-based and inclusive. Attributes such as ID and Parent describe relationships.GGUF.ggufGGUF is a binary container designed for GGML and compatible inference runtimes. Its header contains a format version, tensor descriptions, and key-value metadata; tensor data follows. It is widely used for local inference with llama.cpp-family tools, but the format alone does not guarantee support for every runtime or architecture. The extension also does not indicate whether a model is quantized.GIF.gifGIF is an image format that can contain multiple frames and is commonly used for short looping animation. Because its color palette is limited, it fits simple diagrams and short explanations better than photographs or long motion..gitignore.gitignoreA .gitignore file is a text file of patterns that tell Git to ignore paths that are not already tracked. Git applies patterns from .gitignore files and other exclude sources according to precedence rules. Adding a pattern does not stop Git tracking a file that is already in the index.glTF.gltf · .glbglTF is designed for efficient transfer of 3D assets between creation tools and applications. A .gltf file uses JSON and may reference external buffers or textures, while .glb is a binary container.GML.gml · .xmlGML is an OGC standard for expressing geographic geometry and properties in XML. Application schemas define domain-specific features.GPX.gpxGPX (.gpx) is an XML format for exchanging GPS data between apps and web services. It distinguishes waypoints (locations), routes (planned paths), and tracks (recorded paths). GPX 1.1 uses WGS 84 for coordinates. Map styling and app-specific information may not transfer unchanged, so check the imported data for the intended use.GRIB.grib · .grb · .grib2 · .grb2GRIB (General Regularly-distributed Information in Binary form) is a binary format for exchanging gridded meteorological and geophysical data. Messages contain sections for identification, grid and product definitions, data representation, and values. GRIB1 and GRIB2 differ in specifications and tables; local definitions may also be used, so check the edition and producer's conventions.GTF.gtfGTF is gene annotation text with nine tab-separated columns. Coordinates are one-based and inclusive; attributes include gene_id and transcript_id. Required rows and attributes vary by producer and reader.GZIP.gz · .gzipGZIP compresses data losslessly. A .gz file commonly wraps one file; tar.gz first groups files with tar and then compresses that archive.HDF5.h5 · .hdf5HDF5 (Hierarchical Data Format version 5) is a hierarchical data model and file format for storing large and varied data. Groups form a hierarchy, while datasets store typed arrays with dimensions; groups and datasets can have attributes. HDF5 does not by itself prescribe one domain's coordinate, unit, or semantic conventions.HEIF.heif · .heicHEIF is an image-file framework in the ISO Base Media File Format family. HEIC is a common HEIF-based use that stores HEVC images, so the two terms are related but not identical.HTML.html · .htmHTML is a markup language for describing the structure and meaning of web pages. Keep presentation in CSS and behavior in JavaScript when needed.ICC.icc · .icmICC profiles are data used in color management. Compatible software uses information about devices or color spaces to interpret and transform color. Profiles may be embedded in images or handled separately; they are not image-pixel files.ICO.icoICO is an image container mainly used for Windows icons. It can hold images at multiple sizes and color depths for icon display.iCalendar.icsiCalendar exchanges calendar information such as events, ToDos, and availability. Date, time zone, and recurrence interpretation should be checked after import.IGES.iges · .igsIGES exchanges geometry and product-definition data between CAD/CAM systems. It remains common in established workflows, but converted surfaces and solids need checking.InDesign document.inddINDD is Adobe InDesign's native page-layout document. It stores editable page designs, text, placed objects, and styles for books, magazines, print work, and digital publications. For viewing or print delivery, export to PDF or another suitable format; linked images and fonts may need to be collected separately.INI configuration file.ini · .cfg · .confINI is a conventional name for text configuration files organized as sections and key-value pairs. It has no single universal specification, so comment syntax, delimiters, key casing, and multiline values can vary between applications and parsers.Jupyter Notebook.ipynbJupyter Notebook (.ipynb) is a notebook document format that stores code cells, Markdown cells, metadata, and outputs in a JSON structure. A notebook may contain executable code as well as its visible results, so viewing it and running it are different actions.ISO Image.isoAn ISO image stores optical-media contents and structure in one file. It differs from a compressed archive.JPEG.jpg · .jpegJPEG is a lossy image format used widely for distributing photographs.JSON.jsonJSON is a text format that represents structured data with keys and values. It is widely used for web APIs and configuration files.JSON5.json5JSON5 extends JSON with comments, trailing commas, some unquoted keys, and single-quoted strings. It is intended to make data easier for people to write by hand; it is not simply another name for JSON. Confirm that the receiving tool can parse JSON5.JSON Lines.jsonl · .ndjsonJSON Lines (.jsonl) is a text format with one valid JSON value on each line. It is convenient for logs and incremental processing because a reader can handle records one at a time. The proposed application/jsonl media type is not standardized.JWK.jwk · .jsonA JWK is a JSON object that represents a cryptographic key. It can contain a key type (kty), key ID (kid), and other metadata. A JWKS groups multiple JWKs in a keys array. JWKs are often used to publish public keys; a JWK containing private-key material is sensitive.JPEG XL.jxlJPEG XL is an image coding system defined by the JPEG Committee and can use lossy or lossless compression. Choose it after checking browsers, applications, delivery infrastructure, and recipients.Keras.keras`.keras` is Keras 3's native whole-model save format. It is normally a ZIP archive that brings together model configuration, weights, compile information, and optimizer state when present. Keras documentation describes config, metadata, and weight data in the archive. The file does not necessarily include implementation code for custom layers or custom objects; the loading environment may need those classes and dependencies. Keras provides a safety setting for loading, but that does not make an unknown model or its custom code trustworthy.KML.kmlKML (.kml) is an XML format that describes how geographic information should appear in a map or earth browser. It can represent placemarks, lines, areas, descriptions, styles, and image overlays. GPX focuses on exchanging GPS waypoints, routes, and recorded tracks; KML focuses more on displaying, annotating, and visualizing geographic data.KTX 2.ktx2KTX 2 (.ktx2) is a texture container specified by Khronos. It is designed for passing image textures to GPUs in games and 3D applications, and can store pixel formats, levels, and metadata. The data format and use of supercompression vary by file; the loader needs support from the target GPU, API, or decoder.LAS.lasLAS is an open point-cloud exchange format maintained by ASPRS. Depending on the point data record format, it stores X/Y/Z coordinates and fields such as intensity, return number, classification, GPS time, RGB, scanner details, and extra attributes, alongside headers and variable-length records for metadata. LAS 1.5 and earlier versions differ in supported point records and coordinate-reference requirements, so check compatibility with older software. LAS is ordinarily uncompressed; losslessly compressed LAZ offers a different size and compatibility trade-off.LAZ.lazLAZ compresses LAS point records in chunks. LAZ 1.4 is based on LAS 1.4 and losslessly compresses its point data. Compatible implementations can decompress chunks independently, which may allow point-cloud processing or random access without expanding the entire file. Compression does not change the meaning of LAS coordinate, classification, or other fields, but reader-version support, extended records, and companion waveform data still affect interoperability. LAZ 1.4 does not define all of LAS 1.5, so the extension alone cannot establish compatibility with LAS 1.5 features.LZ4.lz4A .lz4 file usually stores one losslessly compressed data stream in the LZ4 frame format. This article covers official frame specification 1.6.4, not raw blocks or legacy frames.HLS playlist.m3u8`.m3u8` is a text playlist format used by HTTP Live Streaming (HLS). It does not contain the video or audio; tags and URIs point to media segments or other playlists. A master playlist describes variant streams and alternate renditions, while a media playlist lists segments.M4A.m4aM4A denotes an audio-oriented MPEG-4 container. It often holds AAC but may also hold ALAC; the extension alone does not identify the internal codec.M4S media segment.m4s`.m4s` is an extension used for media segments in delivery based on the ISO Base Media File Format (ISO BMFF). A segment contains part of fragmented MP4 audio or video and is referenced by a DASH or HLS manifest. Playback usually also needs initialization data for tracks and codecs, plus a manifest that describes segment order and timing. An `.m4s` file is not itself a playlist such as an MPD or `.m3u8`.M4V.m4vM4V is used for MPEG-4-related video files and may resemble MP4 structurally. The extension alone cannot establish the video/audio codecs, DRM status, or playback support.Markdown.md · .markdownMarkdown is lightweight markup for expressing headings, links, code, and other structure in plain text. CommonMark, GitHub Flavored Markdown, and other dialects can render the same file differently.MAT-file.matA MAT-file (.mat) is MATLAB's binary format for workspace variables. Versions 4, 6, 7, and 7.3 differ in supported arrays and data types, compression, size limits, and partial-access features. Ordinary MATLAB `save` operations default to Version 7; Version 7.3 is HDF5-based and supports large variables and partial access. Because v7.3 and earlier versions use different internals, check the file version and required features instead of inferring compatibility from the extension.MBOX.mbox · .mbxMBOX stores multiple email messages in one file. Mail applications may differ in how they import folders, labels, and message content.MBTiles.mbtilesMBTiles stores map tiles and metadata in a SQLite database. This article covers specification 1.3 and distinguishes image tiles from pbf tiles containing gzip-compressed MVT.MetaImage.mha · .mhdMetaImage is a medical and scientific image format with a tagged text header and pixel data, handled by ITK's MetaIO. A .mha file combines header and pixels; a .mhd file separates the header and usually references a data file such as .raw. The header can record dimensionality, axis sizes, element type, byte order, and spacing.MIDI.mid · .midiA Standard MIDI File stores musical events such as notes, timing, and instrument settings—not an audio waveform. The sound depends on the playback synthesizer and its sound data, so the same file can sound different across systems.MKV.mkvMKV is a Matroska container, not a video codec. It can hold video, multiple audio and subtitle tracks, and chapters; playback depends on the internal formats and player.MOV.movMOV is based on the QuickTime File Format and can hold video and audio. The .mov extension alone does not reveal codecs, track layout, or compatibility with a recipient's tools.MP3.mp3MP3 reduces audio size through lossy encoding. CBR keeps a constant bitrate, while VBR varies allocation with audio complexity; neither restores the discarded source information.MP4.mp4MP4 is an MPEG-4 Part 14 container based on the ISO Base Media File Format. It can hold video and audio, but .mp4 alone does not identify codecs such as H.264, HEVC, AV1, or AAC.MPEG-DASH MPD.mpd`.mpd` is the XML manifest used by MPEG-DASH, formally called a Media Presentation Description (MPD). It describes presentation periods, adaptation sets, representations such as video qualities, and how to locate media segments. The audio and video are stored separately; the MPD tells a player how the presentation is arranged and where to fetch it.MRC.mrcMRC (MRC/CCP4 map and image format) is a binary format used mainly for cryo-electron microscopy images and 3D maps. In MRC2014, a 1,024-byte main header records array dimensions, MODE (the value data type), axis mapping, grid spacing, and extended-header length, followed by the data array. It is closely related to crystallographic CCP4 maps, but do not assume identical conventions or use; check the header and how the consuming software interprets it.MSG.msgAn MSG file stores an Outlook item, which may be an email, appointment, contact, or task. Compatibility outside Outlook varies.MessagePack.msgpack · .mpkMessagePack is a binary serialization format for JSON-like values. It can represent integers, strings, binary data, arrays, and maps, and also defines extension values and timestamps. It is not text and must be read or written with a compatible library. The meaning of data and type mappings can also depend on application-level conventions.MVT.mvtMVT is a Protocol Buffers encoding for geographic vector tiles. Tiles contain named layers, features and attributes.MXF.mxfMXF (Material Exchange Format) is a professional container for exchanging video, audio, and other essence together with structural metadata describing their relationships. SMPTE ST 377-1 defines the common file structure, including partitions and header/body/footer organization, but does not by itself prescribe every essence container or descriptive metadata scheme. Compatibility depends on the combination of operational pattern, essence mapping, codecs, and application specification, so `.mxf` alone does not identify playback support or contents.netCDF.nc · .nc4 · .cdfnetCDF (Network Common Data Form) is a set of formats and software for storing and exchanging scientific data in a self-describing, portable form. A dataset is organized around dimensions, variables, and attributes. The classic data model differs from the extended model available with netCDF-4; netCDF-4/HDF5 files can use groups and other hierarchical features. The extension alone does not identify the file variant.NIfTI.nii · .nii.gz · .hdr · .imgNIfTI, usually NIfTI-1 or NIfTI-2, is a file format for working with neuroimaging data such as MRI and fMRI across analysis software. Its header describes voxel arrays, dimensions, data type, scaling, and mappings from voxel coordinates to anatomical or standard space. NIfTI-1 can combine header and image data in a .nii file or keep them in a .hdr/.img pair; .nii.gz is a single file compressed with gzip.NPY.npyNPY (.npy) is NumPy's binary format for storing a single array. Its header records the format version, dtype, shape, and memory order, followed by the array data. Unlike a text table, it can preserve numeric types and multidimensional shape. NPY is not itself a compressed archive and is normally used for one array per file. Object-dtype arrays may involve pickle, so check object-array and `allow_pickle` handling when loading untrusted input.NPZ.npzNPZ (.npz) is NumPy's ZIP-based archive for storing multiple arrays together. It contains one `.npy` file per array, and NumPy `load` returns an `NpzFile` that can access arrays by name. `savez` writes an uncompressed archive, while `savez_compressed` uses DEFLATE, so the extension alone does not tell you whether entries are compressed. Each array keeps its dtype and shape through NPY. Object-dtype arrays may involve pickle; handle allow_pickle carefully with untrusted input.NRRD.nrrd · .nhdrNRRD (Nearly Raw Raster Data) is a format for N-dimensional raster data used in scientific visualization and image processing. Its text header describes dimensions, type, axis sizes, and data encoding; it can also carry axis labels, units, directions, and spatial origin. Header and data may be combined in a .nrrd file or separated into an .nhdr header and external data file.OBJ.objWavefront OBJ describes polygon meshes and free-form surfaces. Material definitions may be referenced in a separate MTL file, with texture images also needed for the intended appearance.ODP.odpODP is the OpenDocument presentation format. It can contain editable slides, shapes, images, and notes.ODS.odsODS is the spreadsheet format defined by OpenDocument Format and can contain sheets, formulas, and formatting.ODT.odtODT is the text document format defined by OpenDocument Format. Its XML-based package stores text, styles, tables, and images for document creation and editing.OGG.oggOgg is a container format for media streams, not a synonym for the Vorbis codec. An .ogg file can carry different codecs, so identify its contents and playback support.OGV.ogvOGV is an extension for video streams in an Ogg container. The .ogv suffix does not identify the video or audio codec; playback depends on the player's support.ONNX.onnxONNX (Open Neural Network Exchange) is an open model representation for exchanging machine-learning models between frameworks and inference runtimes. A typical `.onnx` file stores a Protocol Buffers ModelProto describing a computation graph, inputs and outputs, types and shapes, opset imports, and initializer tensors. Safetensors primarily stores weight tensors, whereas ONNX represents a model graph as well. Conversion does not make every runtime support all operators or model-specific features; check the IR/opset versions and implementation support.Opus.opusOpus is an IETF-standardized audio codec, not a container. When stored in Ogg, .opus is the recommended extension; playback still depends on the recipient's software.OpenRaster.oraOpenRaster (.ora) is a format for exchanging layered raster images between image-editing applications. Its ZIP container holds files such as stack.xml, which describes the layer structure, and the layer images. It can transfer basic layer information, but does not make every application's effects and editing features universally interchangeable.ORC.orcORC is a typed columnar file format used in analytics systems. Column projection and file indexes can help readers avoid unnecessary data.OTF.otfOTF is a font file associated with OpenType. Features such as alternate glyphs and layout behavior depend on the font and application; the extension alone does not guarantee them.Parquet.parquetApache Parquet stores tabular data by column, organized into row groups and column chunks. Analytics tools can read needed columns without scanning every field.PCAP.pcap · .capPCAP (.pcap) is a widely supported binary format for captured network packets. It records packet data along with link-layer type and timestamps. Its simpler structure is compatible with many older analyzers, but it has fewer ways than PCAPNG to represent details such as multiple interfaces or comments.PCAPNG.pcapngPCAPNG stores packets captured from a network. It is more extensible than classic pcap and can retain details such as multiple interfaces and comments. Captures may contain credentials or personal data, so review them before sharing.PCD.pcdPCD stores point clouds used by PCL. The ASCII header in PCD 0.7 declares point fields and types, WIDTH and HEIGHT, VIEWPOINT and the storage mode.PDF.pdfPDF is widely used to distribute and view documents while preserving their layout. It can hold multiple pages, text, images, and graphics.PEM.pemPEM encodes certificate-related structures as Base64 text between BEGIN and END labels. A .pem extension can contain a certificate, public key, private key, or other material.PFX.pfx · .p12PFX and P12 are extensions for PKCS#12 containers. They may include a private key and certificate chain, so handle the file and password securely.PLY.plyPLY records vertices and, when present, polygon faces. The header declares element counts and properties such as coordinates, normals and colors; faces reference vertex indices.PNG.pngPNG is a lossless raster image format that supports alpha transparency.PPT.pptPPT is the legacy binary presentation format used by older Microsoft PowerPoint versions. For new work, PPTX is usually preferred; for view-only distribution, consider PDF.PPTX.pptxPPTX is an Office Open XML presentation format. It can hold editable slides, themes, shapes, images, notes, and animations.Java Properties.propertiesJava Properties is a line-oriented key-value text format used mainly with Java's Properties API and ResourceBundle. The .properties extension is common, but character encoding depends on the loading method and Java version, so the extension alone is not enough to determine it.Protocol Buffers schema.proto.proto is a schema file that describes Protocol Buffers messages, fields, and types. A compiler such as protoc reads it and generates code for selected languages. The .proto file is not a serialized message; it is normally edited as text.PSD.psdPSD is an Adobe Photoshop document for editable production work. It can preserve layers, masks, text and effects, but is not the usual final image format for browsers or general distribution.RAR.rarRAR is an archive format associated with RARLAB. Creating and extracting archives may depend on different tools and licensing terms; support is not universal.RINEX.rnxRINEX (Receiver Independent Exchange Format) is a text format for exchanging GNSS receiver observations and navigation messages independently of receiver manufacturer. RINEX 4.02, dated September 2025, defines observation, navigation, and meteorological files for multiple satellite navigation systems and signals. Long filenames commonly use .rnx, with an additional suffix such as .gz when compressed. RINEX contains measurement records for processing, not a finished route or map track.RTF.rtfRTF is a rich text format that describes character styling and paragraphs in text. It can exchange basic formatted documents, but does not preserve modern editing features or complex layouts like DOCX.Safetensors.safetensorsSafetensors is a binary format for storing and distributing machine-learning tensor values. A file begins with an 8-byte little-endian header length, followed by a UTF-8 JSON header describing tensor names, dtypes, shapes, and data offsets, then a byte buffer of tensor data. It is not by itself a model architecture or executable program. Unlike pickle-based serialization, it is not designed to restore arbitrary objects by running embedded reconstruction code. That does not prove that a file's source is trustworthy, that every reader is free of defects, or that a model is safe to use.SAM.samSAM (Sequence Alignment/Map) is a tab-delimited text format for sequencing reads and their alignment to reference sequences. Optional header lines describe references and software; each alignment record carries a read name, FLAG, reference and position, MAPQ, CIGAR, sequence, quality, and optional tags. The specification can also represent unmapped reads, so not every record is necessarily aligned. SAM is easy to inspect but can be large; BAM is its binary representation and CRAM adds reference-aware compression.7Z.7z7Z is an archive format used by 7-Zip and compatible tools. Compression and optional encryption settings can vary, so recipients need an extractor that supports the chosen options.Shell Script.sh · .bashA shell script is a text file containing commands interpreted by a shell such as sh or Bash. The .sh extension is common, but it does not identify the shell syntax. Check the target environment, including the shebang, how the script is invoked, permissions, and line endings.Shapefile.shpShapefile stores geometry and attributes across files. Matching .shp geometry, .shx index and .dbf attributes form the core set. Sending only .shp is insufficient.SP3.sp3SP3 (Standard Product 3) is a text format for exchanging epoch-based precise satellite orbits and clock corrections used in GNSS analysis. Its header identifies items such as the version, time system, and satellites; epoch records carry satellite positions and clock information. SP3-d supports up to 999 satellites. An SP3 product is distinct from RINEX receiver observations and is used for precise orbit products from analysis centers.SQL.sqlSQL files contain database commands. Syntax and supported features differ between database products.SQLite database.sqlite · .sqlite3 · .dbSQLite is an embedded relational database stored in a disk file, usually with tables and indexes in one main file. Common extensions include .sqlite, .sqlite3, and .db, but the name alone does not confirm the format.SRT.srtSRT, or SubRip, records cue numbers, time ranges, and subtitle text. It is separate from the video; text encoding and styling behavior can vary across players.STEP.step · .stpSTEP is based on ISO 10303 and is used to exchange 3D geometry and product data between CAD/CAM systems. STEP and STP are common extensions for the same family; native modeling history usually does not transfer.STL.stlSTL describes a solid's surface with triangles in ASCII or binary form. It is widely used for 3D printing, but generally does not convey reliable units, materials, colors, textures, or animation.SVG.svgSVG is an XML-based vector image format. It can preserve sharp outlines when scaled, making it useful for logos, icons, and diagrams rather than photographic images.TAR.tarTAR bundles files, directories, and metadata into one archive. TAR alone does not compress them; tar.gz, tar.bz2, and tar.xz add separate compression layers.TGA.tgaTGA, also called Targa, is a raster format seen in graphics and game-production workflows. Compatible tools can handle alpha channels, but new web images normally use PNG, WebP, or AVIF.3GP.3gp · .3gpp3GP is a multimedia container defined by 3GPP for continuous media. It can store video and audio, but the extension alone does not identify codecs or guarantee playback.3MF.3mf3MF packages a 3D model and manufacturing information for additive manufacturing. Unlike a simple STL workflow, it can carry units and supported materials or colors.TIFF.tif · .tiffTIFF is a tagged raster image format common in scanning, editing, and print production. Its compression, bit depth, color settings, and page structure vary, so the extension alone does not tell you size or quality.TOML.tomlTOML is a text configuration format with key-value pairs, tables, arrays, and typed values. Parser support and application-specific rules can differ.BitTorrent metainfo file.torrentA .torrent file is a BitTorrent metainfo file. It is a bencoded dictionary that describes information such as the content name, piece data, and tracker URLs; it normally does not contain the distributed files themselves. A BitTorrent client reads it to locate peers and verify downloaded data.MPEG-2 Transport Stream.ts`.ts` is a common extension for the MPEG-2 Systems Transport Stream defined by ISO/IEC 13818-1. It packetizes and multiplexes video, audio, and signaling data, with structure intended to help synchronization and recovery in error-prone transmission environments. HLS can use TS media segments; RFC 8216 requires each such segment to contain a single MPEG-2 program and specifies table requirements. `.ts` is also used for TypeScript source files, so the extension alone does not identify the content.TSV.tsvTSV separates columns with tabs and rows with line breaks. The handling of tabs or line breaks inside values and quoting varies by tool.TTF.ttfTTF is a TrueType outline font file used by operating systems and applications. Web delivery may call for WOFF2, subject to licensing and character coverage.TTML.ttml · .xmlTTML represents timed text in XML for subtitles and captions. Profiles define available presentation features, so a .ttml extension alone does not prove the target system supports the file.TXT.txtTXT commonly stores plain text. The extension alone does not determine character encoding, line endings, or document structure.UBX.ubxUBX is a binary protocol between u-blox receivers and hosts. A .ubx log contains the messages actually recorded. This article uses the official ZED-F9P HPG 1.32, protocol 27.31 description as its baseline.USD.usd · .usda · .usdc · .usdzUSD describes scenes assembled from multiple assets with layers, references, and variants. USDA, USDC, and USDZ differ in representation or packaging; application support must be checked.vCard.vcfA VCF file contains vCard contact records. Applications may interpret versions, character encoding, repeated fields, and photos differently.WARC.warc · .warc.gzWARC (Web ARChive file format) aggregates multiple digital resources collected from the Web together with related information. Standardized as ISO 28500, a WARC file concatenates records whose headers describe fields such as date, record type, and content length, followed by a content block. Record types such as response, request, resource, metadata, and revisit capture resources and collection context; content can include images and formats other than HTML. Files are sometimes externally compressed as `.warc.gz`. WARC is not a standalone web-page format that guarantees a complete replay of a site.WebAssembly module.wasm`.wasm` is a common extension for a binary module defined by the WebAssembly Core Specification. WebAssembly is a portable low-level code format used beyond the web, but a file is not executable everywhere by itself. It needs a compatible runtime, and available features and host APIs depend on the embedding environment.WAV.wavWAV is an audio container often used for uncompressed PCM in recording and editing. The extension alone does not guarantee PCM; inspect the internal codec, sample rate, and bit depth.WebM.webmWebM is a subset of Matroska for web media. It may combine VP8, VP9, or AV1 video with Vorbis or Opus audio; WebM itself is not a single codec or a guarantee of smaller files.Web App Manifest.webmanifestA Web App Manifest uses JSON to describe a web application. It can set a name, icons, start URL, and display mode, but its behavior depends on browser and platform support.WebP.webpWebP is an image format designed for web delivery. It can use lossy or lossless compression and supports alpha transparency and animation.WebVTT.vttWebVTT stores timed cues for subtitles and captions. It is served separately from the video and can be used with an HTML track element; it is not a video container.WOFF.woffWOFF packages fonts for browser delivery. WOFF2 uses a different compression format and can reduce transfer size, so compare target browser support and licensing.WOFF2.woff2WOFF2 is a compressed font format for browser delivery. CSS @font-face can load it, but successful use also depends on font licensing, character coverage, and target browser support.WSDL.wsdlWSDL (Web Services Description Language) is an XML format for describing a web service interface and how it can be accessed. It connects abstract operations and messages with bindings for protocols and message formats, endpoints, and service information. A WSDL file is neither the service implementation nor the actual data exchanged.X3D.x3d · .x3dv · .x3dbX3D describes interactive 3D worlds and multimedia. XML, ClassicVRML and binary encodings exist; support depends on the runtime and selected encoding.XCF.xcfXCF is GIMP's native image project format. It preserves editing information such as layers and transparency so work can continue in GIMP. It serves a different purpose from general delivery formats such as JPEG and PNG; export a finished image in a format suited to its intended use.XLS.xlsXLS is the binary spreadsheet format used by older Microsoft Excel versions. It is common in existing workbooks; new work usually uses XLSX or an organization-specified format.XLSX.xlsxXLSX is a spreadsheet format based on Office Open XML. It can keep workbook features that a simple text table does not carry.XML.xmlXML is a markup language that represents structured data with tags. It is used where hierarchical structure and schema validation are needed.XMP.xmpXMP defines a metadata model, representation and core properties. It uses XML/RDF and may be embedded in supported files or stored in sidecars such as .xmp. It is not a replacement for the image itself.XML Schema.xsdXSD (XML Schema Definition) is an XML-based schema language for defining elements, attributes, data types, and constraints in XML documents. An XSD is not the XML instance itself; it is used by an XML Schema validator to check instance documents. Check the schema version, namespaces, and validator support.XZ.xzXZ is a container for compressed data streams, often used with lossless LZMA2 compression. It does not itself archive multiple files; tar.xz compresses a tar archive.YAML.yaml · .ymlYAML is a notation for writing mappings, sequences, and scalar values in a human-readable form. Its use overlaps with JSON, but it is not a superset.Zarr.zarrZarr specifies storage for multidimensional arrays and metadata in chunks. A dataset may be a directory or a set of keys in object storage, not one file. Zarr v2 and v3 differ, so check version and codec support at both ends.ZIP.zipZIP packages files and folders into an archive. Compression methods and optional encryption depend on how the archive was created and what the receiving tool supports.Zstandard.zstZstandard (zstd, .zst) is a lossless compression format. It offers selectable compression levels, frame-based sequential processing, and optional dictionaries for suitable workloads. Speed and compression ratio depend on data, settings, and implementation. A .zst stream does not itself archive multiple files.

Compare formats

Compare similar options by use, compatibility, and editability.

Open the filterable comparison list →

Expand all comparisons on this page (225)
AAC vs MP3AAC and MP3 are lossy audio codecs. Choose by distribution, player, container, and compatibility rather than universal quality claims.See the differences →AAC vs OpusAAC and Opus are both lossy audio codecs, but their common delivery environments differ. AAC is widely used in media containers and device playback; Opus is often considered for low-latency communication and web delivery.See the differences →AI vs EPSAI and EPS are vector formats seen in illustration and print. AI is an Illustrator editing master; EPS exchanges artwork in PostScript workflows.See the differences →AI vs PDFAI is an Illustrator editing source. PDF is a fixed-layout file commonly delivered for viewing or printing. Separate continuing design work from final distribution.See the differences →AI vs PSDAI and PSD are Adobe editing files. AI is primarily for vector shapes and illustrations; PSD is for photo compositing and pixel-based image work.See the differences →AI vs SVGAI and SVG both handle vector artwork. AI is an Illustrator working file; SVG is an open format for web display and broader delivery.See the differences →AIFF vs FLACAIFF is an audio container often used for uncompressed PCM in production. FLAC losslessly compresses PCM audio so a compatible decoder can reproduce the original data.See the differences →AMR vs MP3AMR and MP3 serve different audio workflows. AMR is associated with speech communication; MP3 is widely used for general audio distribution.See the differences →APNG vs WebPAPNG and WebP both support animation and transparency. APNG extends PNG with lossless animation; WebP offers web-oriented lossy and lossless encoding.See the differences →Arrow IPC vs CSVBoth can exchange tabular data, but Arrow IPC is a typed binary columnar format, whereas CSV is plain text with delimited fields.See the differences →Arrow vs netCDFApache Arrow specifies a columnar in-memory format and serialization for interchange and analytical processing across languages. netCDF describes scientific datasets with named dimensions, variables, and attributes for coordinates, time, units, and related metadata.See the differences →Arrow vs ORCApache Arrow is a language-independent columnar memory representation for analytics and data interchange. ORC is a columnar file format that organizes rows into stripes with column data, indexes, and statistics to support analytical reads.See the differences →Arrow IPC vs ParquetBoth Arrow IPC and Parquet handle columnar data, but Arrow IPC is mainly for fast exchange between programs, while Parquet is designed for storing and retrieving analytical data.See the differences →Arrow vs ZarrApache Arrow specifies a language-independent in-memory columnar format and serialization for data interchange. Zarr stores N-dimensional arrays as chunks and metadata in a store.See the differences →AVI vs MOVAVI is a RIFF-based container common in legacy Windows workflows; MOV follows Apple's QuickTime File Format and is common in media production.See the differences →AVI vs MP4AVI and MP4 are video containers. Playback depends on the video and audio codecs inside, not the extension alone.See the differences →AVI vs WebMAVI is a container often found in existing Windows-era video assets and workflows. WebM is a container focused on web delivery. Check the codecs inside and support along the delivery path.See the differences →AVIF vs JPEGAVIF is a newer option for optimizing web images and can support transparency. JPEG is a widely compatible lossy format for photo delivery. Choose based on measured results and audience support.See the differences →AVIF vs WebPAVIF and WebP both target web images and support lossy and lossless options and transparency. Compare quality, size, encoding speed, and support using the same images; serving more than one format may be appropriate.See the differences →Avro vs CBORApache Avro encodes records according to a schema and supports writer/reader schema resolution and container files. CBOR is a general binary format with an extended JSON data model, including direct byte strings and tags.See the differences →Avro vs JSONApache Avro is a schema-based serialization system with compact binary encoding and an object container file that carries its schema. JSON is a human-readable text interchange format; Avro also defines a JSON encoding.See the differences →Avro vs ORCAvro is commonly used to exchange schema-governed records. ORC stores typed data by column for analytical reading.See the differences →Avro vs ParquetAvro serializes schema-governed records; Parquet stores data by column for large-scale analytical reads. Choose by how the data is written and queried.See the differences →Avro vs Protocol BuffersApache Avro associates data with a writer schema and resolves it against a reader schema. Protocol Buffers (Protobuf) generates code from `.proto` definitions and field numbers, then encodes messages in a numbered binary wire format.See the differences →BAM vs CRAMBAM is a BGZF-compressed alignment representation. CRAM uses reference differences and other encodings; preservation depends on writer settings.See the differences →BED vs bigBed: text editing and indexed deliveryBED is interval text; bigBed is indexed binary BED-type data.See the differences →BED vs GFF3: interval extraction and annotation structureBED suits interval selection; GFF3 carries typed annotations, attributes and relationships.See the differences →bedGraph vs bigWig: numeric text and indexed deliverybedGraph is interval-value text; bigWig is an indexed numeric track.See the differences →BMP vs PNGBMP appears in older Windows bitmap workflows. PNG is a lossless format useful for graphics, screenshots, and transparency. Choose by existing requirements or new delivery.See the differences →BMP vs TIFFBMP and TIFF are raster image formats used in different workflows. Inspect the actual file's color, compression, metadata, and recipient software.See the differences →Brotli vs gzipBrotli and gzip are lossless formats used for HTTP delivery. Brotli is common for web-content compression, while gzip has broad compatibility with existing tools.See the differences →Brotli vs ZstandardBrotli and Zstandard (zstd) are distinct lossless stream formats. Brotli is used as HTTP content coding br; Zstandard offers configurable framed compression, streaming, and dictionary workflows.See the differences →BSON vs JSONBSON is a length-prefixed binary document format with JSON-like structures and additional types such as dates, binary values, and ObjectId. JSON is a text format defined by RFC 8259, valued for readability and broad tooling.See the differences →BSON vs MessagePackBSON and MessagePack can both represent binary document-like data, but BSON is a typed document representation associated with MongoDB while MessagePack is a general-purpose object serialization format.See the differences →BUFR vs GRIBBUFR and GRIB are WMO binary meteorological code forms, but BUFR represents varied observations while GRIB is mainly used for regularly distributed grid data.See the differences →BZIP2 vs GZIPBZIP2 and GZIP provide lossless compression for file streams. Actual size, speed, and extraction support depend on the data, settings, and recipient.See the differences →CBOR vs JSONCBOR is a binary interchange format with a data model extending JSON, including values such as byte strings and tags. JSON is a human-readable text interchange format widely used by web APIs and configuration tools.See the differences →CBOR vs MessagePackCBOR and MessagePack both serialize JSON-like values to binary. CBOR standardizes protocol tags and deterministic encoding rules; MessagePack offers compact encoding for general objects.See the differences →CRT vs DERCRT is a common certificate filename extension; DER is a binary encoding for ASN.1 data such as certificates. They describe different things.See the differences →CRT vs PEMCRT is a filename extension commonly used for certificates. PEM is a text encoding that can contain certificates, keys, or related objects; they are not equivalent categories.See the differences →CRT vs PFXCRT/CER commonly identifies an X.509 certificate; PFX/P12 is a container that can bundle certificates and private keys.See the differences →CSR vs CRTA CSR is a certificate signing request submitted for issuance. CRT is an extension commonly used for an issued certificate; their roles differ before and after issuance.See the differences →HTML vs CSSHTML defines a web page’s structure and content; CSS controls its presentation and layout. They are complementary, not competing formats.See the differences →CSV vs JSONCSV represents tabular records; JSON represents structured values such as objects and arrays. Choose based on the shape of the data and the receiving system.See the differences →CSV vs ODSCSV is a text format for exchanging values and does not preserve formulas, formatting, or multiple sheets. ODS is an editable spreadsheet workbook that can retain sheets, formulas, and formatting.See the differences →CSV vs ParquetCSV is a human-readable text format for exchanging tabular values. Parquet is a columnar binary format built for efficient storage and reading in analytics systems. Choose for data handoff or large-scale analysis.See the differences →CSV vs XLSCSV is plain text for exchanging tabular values, while XLS is an older Excel workbook format. Choose based on whether you need only values or workbook features.See the differences →CSV vs XLSXCSV exchanges plain table values. XLSX is a spreadsheet file that can retain formulas, formatting, and multiple sheets.See the differences →DAE vs FBXDAE is the XML-based COLLADA exchange format. FBX is widely used for scene exchange between 3D production tools.See the differences →DDS vs PNGDDS is used for GPU-oriented game textures. PNG is a general lossless image format useful for transparent graphics and web distribution.See the differences →DICOM vs JPEGDICOM is a standard for exchanging medical images with examination attributes; JPEG is an image format for broadly viewing and delivering pixels. Choose by whether the task needs clinical data or a shareable still image.See the differences →DICOM vs TIFFDICOM exchanges medical images and related study and equipment attributes through SOP Classes and Transfer Syntaxes. TIFF is a general raster-image format organized with tags and image directories; it does not replace the DICOM clinical data model.See the differences →DNG vs JPEG: editing source or viewing copyDNG is an open format for camera raw information. JPEG is widely used to view and share rendered images.See the differences →DOC vs DOCXDOC is an older binary Word format. DOCX is the current Word document format based on Office Open XML.See the differences →DOC vs ODTDOC is the legacy binary Word format; ODT is an editable text-document format in the OpenDocument family. App support and fidelity can differ.See the differences →DOC vs RTFBoth DOC and RTF store documents, but DOC is the binary format used by Word 97–2003, while RTF is intended to move formatted text between different applications. Choose based on the recipient's software and the features you need to retain.See the differences →DOCX vs HTMLChoose DOCX for word-processing and review; choose HTML for content displayed in a web browser.See the differences →DOCX vs MarkdownDOCX supports editable documents with tables, images, and formatting. Markdown is lightweight plain-text markup suited to text-based review and version control.See the differences →DOCX vs RTFDOCX is a current document format for continued editing with body text, styles, tables, and images. RTF supports basic character and paragraph formatting for document exchange, but is not suited to advanced editing features or complex layout fidelity.See the differences →DWG vs DXFDWG is widely used as a native CAD drawing format. DXF is designed to exchange CAD data between applications. Choose based on the receiving software and the drawing elements that must survive.See the differences →DWG vs STEPDWG is a native CAD drawing format common in AutoCAD workflows; STEP is a neutral exchange format for product and 3D CAD data.See the differences →DXF vs IGESDXF and IGES are exchange formats for moving design data between CAD systems. DXF is widely used for CAD drawings, including in AutoCAD-related workflows; IGES has long been used to exchange geometry such as curves and surfaces. The receiving software and required geometry should determine the choice.See the differences →E57 vs LASE57 exchanges scan points, images and acquisition information. LAS standardizes LiDAR and other point records and attributes; overlapping uses do not mean identical structures.See the differences →EML vs MBOXEML commonly stores one email message. MBOX groups multiple messages in a mailbox file. Choose by the unit you need to preserve or move.See the differences →EPS vs PDFEPS and PDF may both appear in print workflows. EPS exchanges artwork in PostScript-based production; PDF distributes fixed-layout documents and finished deliverables.See the differences →EPS vs SVGEPS and SVG both carry vector artwork, but EPS targets PostScript print workflows while SVG is an open vector format for browsers and web delivery.See the differences →EPUB vs DOCXEPUB is an e-book package for reading apps; DOCX is a word-processing document intended for continued editing. Choose between reader-focused delivery and document editing.See the differences →EPUB vs PDFEPUB and PDF both distribute documents, but EPUB can reflow text for a reading screen while PDF preserves a fixed page layout.See the differences →FASTA vs FASTQ: sequences and quality retentionFASTA alone stores sequences; FASTQ stores sequences with per-base quality scores.See the differences →FBX vs glTFFBX is used to exchange 3D production scenes; glTF is designed for efficient runtime delivery of 3D assets.See the differences →FBX vs OBJFBX may carry scene data such as rigs and animation; OBJ is commonly used for mesh geometry and may reference materials separately.See the differences →FIT vs GPXFIT is a binary format for sports-device activity, sensor, and event data; GPX is XML for exchanging waypoints, routes, and tracks.See the differences →FITS vs HDF5FITS is a standard for exchanging, analyzing, and archiving astronomy data, with headers and one or more Header/Data Units (HDUs). HDF5 is a general hierarchical container in which applications define data structures and meaning.See the differences →FITS vs netCDFFITS is a standard for exchanging, analyzing, and archiving astronomy data, with image arrays and tables in Header/Data Units (HDUs). netCDF describes scientific data using dimensions, variables, and attributes and is used in fields such as meteorology and Earth science.See the differences →FITS vs ZarrFITS is a standard for astronomy data organized into Header/Data Units (HDUs). Zarr stores multidimensional arrays as chunks and metadata under keys in a store.See the differences →FLAC vs AACFLAC uses lossless compression, while AAC is a lossy audio codec. Separate preservation needs from delivery size and playback compatibility.See the differences →FLAC vs WAVFLAC is a lossless compression format that can reconstruct the original PCM audio. WAV is an audio container commonly used for uncompressed PCM, but its internal codec should be checked.See the differences →FlatGeobuf vs GeoPackage: delivery and SQL managementFlatGeobuf is a binary feature collection; GeoPackage is a SQLite database for geographic data.See the differences →FLV vs MP4FLV is mainly encountered in legacy Flash Video files, while MP4 is a widely used container for current video delivery. A migration decision should account for the codecs inside the file, not only its extension.See the differences →GeoJSON vs JSONGeoJSON is a JSON-based format with conventions for geographic features and geometries. General JSON can represent many kinds of structured data but does not by itself define coordinate or geometry semantics.See the differences →GeoPackage vs GeoJSONBoth represent geographic data, but GeoPackage is an SQLite-based multi-layer container, whereas GeoJSON is a JSON text format for geographic features.See the differences →GeoPackage vs KMLBoth describe geographic information, but GeoPackage is a SQLite database for multiple layers and tiles, while KML is XML for visualizing geographic data in map and Earth-browser applications.See the differences →GeoParquet vs GeoPackage: columnar analysis and GIS managementGeoParquet adds geographic conventions to Parquet; GeoPackage manages geographic data in SQLite.See the differences →GeoTIFF vs netCDFGeoTIFF uses TIFF imagery and tags to relate raster pixels to geographic coordinates and a CRS. netCDF describes scientific datasets with named dimensions, variables, and attributes, and can group multiple variables and times.See the differences →GeoTIFF vs TIFFGeoTIFF is TIFF with geospatial reference tags; an ordinary TIFF raster may contain no map coordinates.See the differences →GeoTIFF vs ZarrGeoTIFF adds georeferencing and coordinate reference information to TIFF imagery. Zarr stores multidimensional arrays as chunks and metadata; geospatial meaning depends on additional conventions.See the differences →GGUF vs Safetensors: inference delivery and weight storageGGUF delivers inference models to compatible GGML-based implementations. Safetensors stores named tensors; model definitions and execution environments are supplied separately.See the differences →GIF vs APNGGIF and APNG can both contain multiple frames. GIF is broadly recognized for simple short loops; APNG extends PNG for animation with lossless frames and transparency. Compare the target support and actual file size.See the differences →GIF vs BMPGIF and BMP are raster image formats with different strengths. GIF suits palette-based images and simple animations; BMP stores bitmap pixel data in forms whose color depth and compression vary. Choose for the content, size, and target software.See the differences →GIF vs WebPGIF and WebP are used to deliver still and animated images. Compare transparency, animation, target support, and size using the actual asset.See the differences →glTF vs OBJglTF packages 3D assets for web and real-time viewing, including supported materials and animation. OBJ is a broadly used mesh format focused mainly on geometry.See the differences →glTF vs USDglTF is designed to deliver 3D models and scenes efficiently to applications. USD is a scene-description framework for composing assets and layers, often used in larger production and collaboration workflows.See the differences →GML vs GeoJSON: schemas and coordinate systemsGML describes features using XML and application schemas. GeoJSON represents geometry and properties in JSON; this comparison uses the coordinate rules of RFC 7946.See the differences →GPX vs KMLGPX is XML for exchanging GPS waypoints, planned routes, and recorded tracks. KML describes geographic features for map or globe display and can include names, descriptions, styles, folders, and overlays.See the differences →GRIB vs netCDFBoth are used for weather and Earth-science data, but GRIB commonly packages gridded forecast messages while netCDF describes datasets with dimensions, variables, and attributes.See the differences →GRIB vs ZarrGRIB exchanges weather forecast and analysis grids as messages with product, grid, and data-representation information. Zarr stores multidimensional arrays as chunks and metadata under keys in a store.See the differences →GTF vs GFF3: attribute syntax and transcript mappingBoth use nine annotation columns, but attribute syntax and relationship models differ.See the differences →GZIP vs XZGZIP and XZ are lossless compressors commonly applied to a single file. Their practical trade-offs include output size, compression and extraction time, and support on the recipient's systems.See the differences →GZIP vs ZIPGZIP commonly compresses one file, while ZIP can package multiple files and directories together. The right choice depends on whether the recipient needs a bundle, the expected tools, and the delivery workflow.See the differences →HDF5 vs netCDFHDF5 is a general container for hierarchical data; netCDF provides a scientific data model and APIs. netCDF-4 uses HDF5 as its storage foundation, but an arbitrary HDF5 file is not necessarily readable as netCDF-4.See the differences →HDF5 vs ZarrHDF5 organizes groups and datasets hierarchically in a general container. Zarr represents chunked multidimensional arrays and metadata as separate keys in a store, with filesystem and object-store use in mind.See the differences →HEIF vs AVIFHEIF is a flexible image-container family, while AVIF follows the AV1 Image File Format specification. Their support varies across cameras, operating systems, browsers, and editing tools.See the differences →HEIF vs JPEGHEIF can store images efficiently and may support features beyond a basic still image, while JPEG remains widely supported for sharing and publishing. The best choice depends on the camera workflow and every destination that must open the file.See the differences →HEIF vs WebPHEIF is common in some camera and mobile photo workflows, while WebP is designed for web images and supports still and animated content. Compatibility depends on the actual codec, application, browser, and delivery path.See the differences →HTML vs MarkdownHTML describes structured web content and provides detailed control over elements, while Markdown offers a compact authoring syntax that is commonly converted to HTML. The best choice depends on who edits the content and how it is published.See the differences →ICO vs PNGICO is a Windows icon container that can hold multiple image representations at different sizes and color depths. PNG is a general-purpose raster image format with broad support and transparency, but it does not by itself define an icon set for every operating system.See the differences →ICS vs CSVICS represents calendar events and scheduling data with fields for dates, recurrence, time zones, and other event details. CSV stores rows and columns, so calendar applications may require a specific column layout and mapping to import it.See the differences →ISO vs ZIPISO commonly represents a disc image with a filesystem layout that can be mounted or written to media. ZIP is a file archive for bundling and optionally compressing files and directories. They serve different packaging needs even when both contain similar files.See the differences →JPEG vs BMPJPEG is a lossy format commonly used for photographs and compact distribution; BMP is a family of bitmap formats used in some Windows workflows.See the differences →JPEG vs PNGJPEG commonly uses lossy compression and suits many photographs, while PNG preserves pixel values losslessly and supports transparency. The choice depends on image content, editing needs, and the destination's requirements.See the differences →JPEG vs TIFFJPEG is widely used to deliver photos efficiently, while TIFF is common in scanning, print, and image-production workflows. Choose by the delivery or production task, and check TIFF's compression and color settings.See the differences →JPEG vs WebPJPEG is widely supported for photographs, while WebP can use lossy or lossless compression and supports transparency. For web delivery, results depend on the source image, encoder settings, and target browsers.See the differences →JSON vs TOMLJSON is widely used for APIs and program-to-program data exchange. TOML is designed for human-edited application configuration, with readable keys, values, tables, and arrays.See the differences →JSON vs YAMLJSON is a strict text format widely used for APIs and data exchange between programs. YAML offers syntax suited to human-edited configuration and structured data. Choose for the ecosystem and workflow.See the differences →JSON5 vs JSONJSON5 keeps JSON's data model while adding hand-editing conveniences such as comments, identifier keys, single-quoted strings, trailing commas, and hexadecimal numbers. Standard JSON uses stricter syntax and is widely supported by APIs and general-purpose parsers.See the differences →JSON Lines vs AvroJSON Lines stores one JSON value per UTF-8 line for record-by-record processing. Avro encodes typed records using a writer schema and can store schema metadata with data blocks.See the differences →JSON Lines vs CSVJSON Lines places one independent JSON value on each line, while CSV arranges fields into rows and columns. JSON Lines handles nested or varying record structures more naturally; CSV suits tabular data with consistent columns.See the differences →JSON Lines vs JSONJSON Lines (newline-delimited JSON) is a UTF-8 text convention that places one independent valid JSON value on each line. A regular JSON text represents one value as a whole, so JSON Lines suits sequential processing and appending multiple records.See the differences →JSON Lines vs ParquetJSON Lines stores an independent JSON value on each UTF-8 text line. Parquet is a binary column-oriented file with row groups and column chunks.See the differences →JPEG XL vs AVIFJPEG XL and AVIF are distinct image coding formats with different feature sets and implementation support. The practical choice depends on browsers, applications, encoders, and the delivery path, not just a codec's advertised capabilities.See the differences →JPEG XL vs JPEGJPEG XL and JPEG are distinct image formats. JPEG remains broadly supported, while JPEG XL may be considered where receiving browsers and applications support it. Compare actual encodings instead of assuming size or quality from the format name.See the differences →JPEG XL vs PNGPNG is a widely supported lossless raster format with transparency. JPEG XL is a newer image coding format with different compression and feature options, but client support must be checked. The right choice depends on editing, delivery, and fallback needs.See the differences →JPEG XL vs WebPJPEG XL and WebP are different image formats with distinct feature sets and support across browsers and tools. WebP is established in many web workflows; JPEG XL may be considered only where client support and the full delivery pipeline are confirmed.See the differences →Keras vs ONNX: training saves and inference exports.keras saves model configuration, weights and any optimizer state in Keras. ONNX represents computation graphs for compatible runtimes.See the differences →LAS vs LAZLAS stores point records without compression; LAZ losslessly compresses supported LAS data. Reader compatibility matters as well as size.See the differences →LZ4 vs Zstandard: frame compatibility and settingsBoth are lossless, but LZ4 frames and Zstandard frames are not byte-compatible.See the differences →M4A vs MP3M4A is a filename extension commonly used for audio in an MPEG-4 container, while MP3 names an audio coding format. An M4A file may contain AAC, ALAC, or another supported codec, so the extension alone does not identify its encoding.See the differences →M4A vs WAVM4A and WAV are audio containers; the extension alone does not identify the codec or quality. Consider delivery size and compatibility versus recording and editing needs.See the differences →M4V vs MP4M4V and MP4 are filename extensions used for MPEG-4-family video files. The extension alone does not establish the internal codecs, playback compatibility, or whether content protection is present; inspect the actual file and target environment.See the differences →MBOX vs MSGMBOX typically stores multiple email messages in a mailbox file, while MSG is commonly used for an individual Outlook item. Choose according to the unit being migrated and the destination application's import support.See the differences →MBTiles vs MVT: tilesets and tile encodingMBTiles is a tileset in SQLite; MVT encodes vector tiles. They occupy different layers and can be used together.See the differences →MIDI vs WAVBoth are used for music, but MIDI stores performance events while WAV stores audio samples for playback.See the differences →MKV vs MP4MKV and MP4 are containers that can hold video, audio, subtitles, and metadata. MKV often supports a flexible mix of tracks, while MP4 is widely used for delivery across devices and services. Compatibility depends on the codecs and track features inside the file.See the differences →MKV vs WebMMKV is a flexible Matroska container; WebM is a constrained profile of Matroska intended for web media.See the differences →MOV vs MKVMOV and MKV are containers that can store video, audio, subtitles, and metadata. MOV is common in Apple-oriented capture and editing workflows, while MKV is often used for flexible combinations of tracks. Compatibility depends on the actual codecs and target applications.See the differences →MOV vs MP4MOV and MP4 are container formats, not video codecs. MOV is common in QuickTime-oriented capture and editing workflows, while MP4 is widely used for general distribution. Playback depends on the actual video and audio codecs inside the file.See the differences →MP3 vs FLACMP3 uses lossy audio compression to reduce file size; FLAC compresses audio losslessly and can restore the original PCM samples. Choose according to delivery size, playback support, and whether an editing or archival master must be preserved.See the differences →MP3 vs OpusMP3 is a lossy audio format with broad support across devices and software. Opus is designed for efficient coding in uses such as voice communication and streaming, including low-latency scenarios. Choose for the delivery environment.See the differences →MP3 vs WAVMP3 is a lossy audio coding format commonly used for compact delivery. WAV is a container often used for recording and editing, frequently carrying uncompressed PCM audio but capable of other encodings. Check the actual audio data and workflow requirements.See the differences →MP4 vs WebMMP4 and WebM are containers for audio and video, not single codecs. MP4 is widely used across devices and services; WebM is a Matroska-based subset associated with web delivery. Size and quality depend on the encoded streams, settings, and playback environment.See the differences →MPD vs M3U8MPD is DASH's XML manifest. M3U8 is a UTF-8 playlist; this comparison covers its HLS use. Neither is the media payload.See the differences →MSG vs EMLMSG stores Outlook items and can represent more than email, including appointments and contacts. EML is commonly used to save or transfer one internet email message at a time.See the differences →MVT vs GeoJSON: tile delivery and data exchangeMVT is a Protocol Buffers encoding for map vector tiles. GeoJSON is geographic JSON data and does not itself define tile delivery rules.See the differences →netCDF vs ParquetnetCDF describes scientific datasets with named dimensions, variables, and attributes that can relate coordinates and time. Parquet is a columnar file format with row groups and column chunks, suited to selecting columns in analytical queries.See the differences →netCDF vs ZarrnetCDF provides a scientific data model with dimensions, variables, and attributes across several file formats. Zarr specifies chunked multidimensional arrays stored in key-value systems. The better fit depends on tools, storage, and access patterns.See the differences →NIfTI vs DICOMBoth appear in medical imaging, but NIfTI mainly carries neuroimaging voxel arrays and spatial transforms, while DICOM exchanges clinical studies with related attributes.See the differences →NPY vs NPZNPY stores one array with dtype and shape. NPZ bundles NPY members in ZIP and provides access by array name.See the differences →NPZ vs HDF5: array bundles and partial readsNPZ bundles named NPY arrays in ZIP. HDF5 organizes groups, datasets, and attributes hierarchically.See the differences →ODP vs PPTXODP is the OpenDocument presentation format, while PPTX is based on Office Open XML. Both store slide decks, but editing behavior and feature support depend on the presentation software and organization workflow.See the differences →ODS vs XLSXODS is the OpenDocument spreadsheet format, while XLSX is based on Office Open XML. Both support editable workbooks, but feature behavior and rendering can vary across spreadsheet applications and versions.See the differences →ODT vs DOCXODT is an editable word-processing format in the OpenDocument family. DOCX is an editable document format based on Office Open XML. Choose for your software, collaborators, and organizational requirements.See the differences →ODT vs PDFODT is an editable OpenDocument text format, while PDF is commonly used to preserve a page layout for viewing and distribution. Choose based on whether recipients need to revise the content or see a consistent rendition.See the differences →ODT vs RTFODT is an editable document package based on the OpenDocument standard and can include text, tables, images, and styles. RTF exchanges basic character and paragraph formatting as text.See the differences →Ogg vs MP3Ogg is a container that can carry codecs such as Vorbis or Opus; MP3 is a lossy audio format. The Ogg extension alone does not identify its codec, so check the actual stream and target-player support.See the differences →Ogg vs OpusOgg is a container; Opus is an audio codec. They serve different roles rather than competing as equivalent formats. An Opus stream may be stored in Ogg or handled with an .opus file, depending on the workflow.See the differences →OGV vs WebMOGV and WebM are video containers, not guarantees of a particular codec or playback result. The usable video and audio codecs, browser versions, and delivery setup determine compatibility.See the differences →ORC vs CSVORC is a typed columnar binary format suited to analytical systems that read selected columns. CSV is a text format for rows and delimited fields that people and general-purpose tools can handle easily.See the differences →Parquet vs JSONParquet is a binary columnar format for analytics; JSON is a text format for structured-data exchange. Parquet is often used for large analytical datasets, while JSON is common in APIs and configuration.See the differences →Parquet vs ORCParquet and ORC are columnar formats for large-scale analytical data. Choose according to the query engine, existing platform, and measured workload.See the differences →Parquet vs ZarrApache Parquet stores tables in files divided into row groups and column chunks. Zarr stores multidimensional arrays as chunks with array metadata in a store.See the differences →PCAP vs PCAPNGPCAP is a widely supported classic packet-capture format; PCAPNG is extensible and can retain multiple interfaces and more capture metadata.See the differences →PDF vs DOCXPDF is suited to distributing a reviewed page layout; DOCX is suited to creating and revising a document. Choose by what the recipient needs to do.See the differences →PDF vs MarkdownPDF distributes a fixed page presentation, while Markdown is plain-text source for structured content that can be edited and rendered in different ways. Choose by whether the priority is final appearance or maintainable text.See the differences →PDF vs PNGChoose PDF for paginated documents and print-ready layouts; choose PNG for screenshots, pixel artwork, or transparency.See the differences →PDF vs SVGUse PDF to share or print page layouts; use SVG for scalable logos, icons, and diagrams on the web.See the differences →PEM vs DERPEM and DER can represent the same certificate or key data in different encodings. PEM wraps Base64 text in labeled boundaries; DER is a binary ASN.1 encoding. The extension alone does not identify the contained object.See the differences →PEM vs PFXPEM is a text encoding for certificate-related structures; PFX/P12 is a PKCS#12 container that can package certificates and private keys.See the differences →PLY vs PCDPLY handles vertices and faces; PCD handles point fields and organization for PCL. Both can store points, but their structures differ.See the differences →PNG vs AVIFPNG is a widely supported lossless raster format with transparency. AVIF is a newer image format that can reduce file size, but support and encoding choices matter. Compare actual images and delivery requirements.See the differences →PNG vs GIFPNG is suited to lossless still images and transparency; GIF supports simple multi-frame animation with a limited color palette. Choose based on still image versus short motion.See the differences →PNG vs SVGPNG is a raster image made of pixels; SVG describes vector shapes that can scale without a fixed pixel grid. Choose based on whether the asset is pixel-based artwork or geometry that should remain sharp at different sizes.See the differences →PNG vs WebPBoth PNG and WebP can support transparency. PNG is a widely supported lossless format; WebP is an option for optimizing web delivery and can also support animation. Compare real assets and target browsers.See the differences →PPT vs ODPPPT is the binary presentation format used by PowerPoint 97–2003, while ODP is the OpenDocument presentation format. When exchanging files between applications, check more than whether the file opens: layout and features may differ.See the differences →PPT vs PPTXPPT is the older binary PowerPoint format; PPTX is the newer Office Open XML presentation format. Choose based on the software and recipients, then test converted slides in the actual presentation environment.See the differences →PPTX vs PDFPPTX is an editable slide deck; PDF is suited to sharing a fixed-looking version for viewing or print. Choose whether recipients need the source or a reviewed final copy.See the differences →Protocol Buffers vs JSONProtocol Buffers defines typed messages from `.proto` schemas and provides a field-number-based binary wire format plus a separate ProtoJSON mapping. JSON is a general text format under RFC 8259 and does not assume a particular schema.See the differences →PSD vs JPEGPSD is an editable Photoshop project that can retain layers; JPEG is a widely shared raster image often used for photographs. Keep the working file separate from the export.See the differences →PSD vs PNGPSD is an editable Photoshop working file that can retain layers and text; PNG is a lossless raster image for viewing and sharing, including transparency. Keep the source and use each for its role.See the differences →PSD vs TIFFPSD is a Photoshop working format that can retain layers and masks; TIFF is commonly used in print, scanning, and image exchange and can use different compression and color settings. Choose for the required workflow.See the differences →RAR vs 7ZRAR and 7Z are archive formats that bundle files and may compress them. The practical choice depends on creation and extraction tools available to both sender and recipient, plus operational needs such as splitting or encryption.See the differences →RAR vs ZIPRAR and ZIP both bundle files into archives. ZIP is broadly supported across operating systems and tools, while RAR may fit workflows that rely on RAR-specific features. Choose for recipient access and handling needs.See the differences →RINEX vs SP3: observations and orbit productsRINEX exchanges observations, navigation and other data. SP3 records satellite positions and clock information by epoch. Their GNSS roles differ.See the differences →RTF vs TXTRTF can store basic text formatting; TXT stores plain characters without rich formatting. Choose based on whether appearance or simple text portability matters.See the differences →Safetensors vs ONNX: weights or model graphsSafetensors stores named tensors. ONNX represents a model with a computation graph, inputs, outputs, and operator versions.See the differences →SAM vs BAMSAM and BAM represent the same alignment information. SAM is TAB-delimited text; BAM is binary encoded in BGZF blocks.See the differences →7Z vs ZIP7Z and ZIP both bundle multiple files. 7Z suits workflows that need flexible compression settings, while ZIP is often easier to extract across operating systems without extra software.See the differences →Shapefile vs GeoPackage: file sets and attribute preservationShapefile is a multi-file layer; GeoPackage holds multiple kinds of geographic data in SQLite.See the differences →SQLite vs CSVSQLite is a relational database file that stores tables, indexes, and schema. CSV is text for exchanging row-and-column values; by itself, it does not preserve database relationships or constraints.See the differences →SRT vs TTMLSRT and TTML both time subtitles to media. SRT is a simple exchange format; TTML is XML-based and can carry richer presentation information when supported by a profile.See the differences →SRT vs WebVTTSRT is a simple text format widely used to exchange subtitles. WebVTT is designed for subtitle tracks in web video, including HTML video workflows. Choose for the player and features you need.See the differences →STEP vs DXFSTEP is commonly used to exchange 3D product and part data; DXF is used for drawing entities and drafting exchange. Choose based on whether the recipient needs a 3D model or drawing content, and verify units and scale.See the differences →STEP vs IGESSTEP and IGES are both used to exchange CAD data. STEP is a modern product-data standard; IGES remains in established workflows for geometry exchange. Choose for recipient requirements and verify units and the imported model.See the differences →STEP vs STLSTEP exchanges product geometry and related data between CAD systems. STL represents a surface as a triangular mesh. They serve different tasks: design-data exchange and preparing geometry for 3D printing.See the differences →STL vs FBXSTL is a triangle-mesh format commonly used to pass a finished shape to 3D printing. FBX can exchange richer production scene data such as materials, rigs, and animation, depending on the tools. Choose by the required downstream use.See the differences →STL vs OBJSTL is common for sending triangle meshes to 3D printing; OBJ can carry mesh attributes and may reference materials separately.See the differences →SVG vs WebPSVG describes vector shapes; WebP is primarily a raster image format. Logos and diagrams often start as vectors, while photos and pixel artwork are raster. Choose for the content and test the target browsers.See the differences →TAR vs 7ZTAR primarily bundles files and metadata; compression is often applied separately, as in tar.gz. 7Z is an archive format with built-in compression options. Choose for the recipient’s tools and the workflow.See the differences →TAR vs ZIPTAR and ZIP both bundle multiple files, but TAR is primarily an archive container and commonly pairs with a separate compressor. ZIP combines archiving and compression in one format. Choose based on recipient tools and the workflow.See the differences →TGA vs PNGTGA appears in some graphics and game-production workflows, while PNG is broadly supported for transparent images and web use. Choose for the target tools and verify color and alpha handling.See the differences →3GP vs MP43GP and MP4 are related ISO-based media container formats, but target uses and playback support differ. The codecs inside the container matter as much as the extension.See the differences →3MF vs STL3MF can carry 3D printing information such as units, materials, and color; STL focuses on triangle-mesh geometry. Choose based on slicer and printer support and which manufacturing details need to travel with the model.See the differences →TIFF vs PNGTIFF is used in print, scanning, and production workflows with configurable compression and color settings. PNG is convenient for general graphics and transparent web images. Neither extension alone determines quality or size.See the differences →TIFF vs WebPTIFF is commonly used in scanning, image editing, and print workflows. WebP targets web delivery and supports lossy or lossless compression, transparency, and animation.See the differences →TSV vs CSVTSV and CSV are plain-text formats for rows and columns. TSV separates fields with tabs, while CSV uses commas and has broad support across spreadsheet and data tools.See the differences →TTF vs OTFTTF and OTF are font file extensions used on desktops and in creative work. Under modern OpenType specifications, a TTF file can also be an OpenType font, so the extension alone does not determine its capabilities.See the differences →TTF vs WOFF2TTF is a TrueType font file commonly installed on desktops and used by applications. WOFF2 is a compressed format designed for web font delivery. Choose for where the font will be used and check its license.See the differences →TTML vs WebVTTTTML is an XML-based timed-text specification used with profiles for caption and broadcast workflows. WebVTT is a practical format for subtitle tracks in web video.See the differences →TXT vs MarkdownTXT stores unformatted text, while Markdown adds lightweight notation for document structure. Both remain plain text, but Markdown's headings, links, and code markers need a compatible renderer to appear formatted.See the differences →UBX vs RINEX: receiver logs and observation exchangeUBX is u-blox-specific binary communication and logging. RINEX is text exchange for observations, navigation and other data.See the differences →USD vs FBXUSD is a scene-description foundation for composing multiple assets, while FBX is widely used to exchange 3D production data. Their fit depends on the pipeline and on what the receiving tools preserve.See the differences →VCF vs CSVVCF is used to exchange contact records, while CSV represents tabular data. Choose based on whether contacts will be imported into an address book or organized and processed as a list.See the differences →WAV vs AACWAV is an audio container often used for uncompressed PCM editing material. AAC is an audio compression codec commonly stored inside containers such as M4A or MP4. They are not the same kind of format, so inspect both the container and the encoded stream.See the differences →WAV vs AIFFWAV and AIFF are audio containers often used for PCM, but either can hold different encodings. The extension alone does not guarantee quality.See the differences →WAV vs OggWAV is a RIFF-family container often used for uncompressed PCM recording and editing. Ogg is a container for audio and other media, commonly paired with codecs such as Vorbis or Opus for delivery. The extension alone does not identify the encoding or sound quality.See the differences →Web App Manifest vs JSONA Web App Manifest is a JSON-based configuration format for web apps, while JSON is a general-purpose data notation. The manifest defines recognized web-app metadata such as name, icons, and start_url.See the differences →WOFF vs WOFF2WOFF and WOFF2 are formats for delivering fonts on the web. WOFF2 is newer and can reduce transfer size, but browser coverage, existing environments, and licensing still guide the choice.See the differences →X3D vs glTFX3D is a standard for representing interactive 3D scenes, while glTF is a format for delivering 3D assets to web and real-time viewers.See the differences →XLS vs ODSXLS is a legacy binary workbook format from Microsoft Excel; ODS is an editable spreadsheet format in the OpenDocument family. Choose based on existing XLS files or an OpenDocument workflow.See the differences →XLS vs XLSXXLS is the older binary Excel workbook format, while XLSX is a spreadsheet format based on Office Open XML. Both can store formulas and formatting, but XLSX is the current choice for most modern Excel workflows.See the differences →XML vs CSVXML represents structured data with hierarchy, elements, and attributes; CSV represents values in a flat table. Choose according to the receiving specification and the structure the data needs.See the differences →XML vs JSONXML and JSON are text formats for structured data, but use different structures and conventions.See the differences →YAML vs TOMLYAML and TOML are both text formats used for human-edited configuration. YAML supports flexible hierarchical structures; TOML emphasizes explicit, readable settings with keys and tables. Choose for the tool and data shape.See the differences →YAML vs XMLYAML and XML both represent structured data. YAML is often convenient for human-maintained configuration, while XML is common in integrations that depend on elements, attributes, schemas, or namespaces.See the differences →Zstandard vs gzipZstandard and gzip are both lossless compression formats. Zstandard has configurable levels, frames, and optional dictionaries; gzip is widely supported by older tools and web delivery systems.See the differences →Zstandard vs xzZstandard and xz are lossless compression formats for files or tar streams. Zstandard is configurable for speed and streaming; xz is commonly used where xz-compatible distribution and compression settings are required.See the differences →

Browse by purpose

Start with what you need to make.

Open the filterable guide list →

Expand all guides on this page (54)
Checks before handing off an AI modelRead the guide →Choose a format for analytics and data exchangeRead the guide →Choose a format for animationRead the guide →Choosing an Archive FormatRead the guide →Testing extraction and contents before archive handoffRead the guide →Choose an audio distribution formatRead the guide →Checking audio masters before handoffRead the guide →Choose an audio preservation formatRead the guide →Choose an audio streaming formatRead the guide →Choose a CAD exchange formatRead the guide →Choose a calendar or contact file formatRead the guide →Verifying calendar and contact data with a trial importRead the guide →Choose a certificate or key file formatRead the guide →Choose a compression or disk image formatRead the guide →Choose a configuration file formatRead the guide →CSV formula injection and safer exportsRead the guide →Choosing a Data Exchange FormatRead the guide →Choose a design production formatRead the guide →Where to keep configuration and secretsRead the guide →Choose a document delivery formatRead the guide →Choose a document editing formatRead the guide →Choosing an Ebook FormatRead the guide →Checking versions, display and hidden data before document handoffRead the guide →Verifying messages after an email migrationRead the guide →Choose a format for saving or migrating emailRead the guide →Checking EPUB structure and reading order before handoffRead the guide →Handing off genomic annotations and signal tracksRead the guide →Checks before handing off GIS dataRead the guide →Preparing and handing off GNSS post-processing dataRead the guide →Choose web-image compression and animation formatsRead the guide →Choose an Office editing formatRead the guide →Sharing Packet Captures SafelyRead the guide →Checking settings and rendering before photo-editing handoffRead the guide →Choose a photo file formatRead the guide →Handing Off Point Clouds with LAS, LAZ and E57Read the guide →Checking dependencies and playback before presentation handoffRead the guide →Checks before handing off scientific arraysRead the guide →Choosing Sequencing Files by WorkflowRead the guide →Choosing a Spreadsheet Exchange FormatRead the guide →Checking values and formulas before spreadsheet handoffRead the guide →Checking an HLS or DASH package before handoffRead the guide →Choosing a Subtitle FormatRead the guide →Checking subtitle timing and display before handoffRead the guide →Handing off 3D assets with their dependenciesRead the guide →Choose a 3D file formatRead the guide →Choose a 3D printing formatRead the guide →Choose a transparent image formatRead the guide →Choose a video container formatRead the guide →Choose a video distribution formatRead the guide →Handing off and testing a web archiveRead the guide →Choosing Web Data and Configuration FormatsRead the guide →Checking missing glyphs and fallbacks in web-font deliveryRead the guide →Choosing a Web Font FormatRead the guide →Choose a web image formatRead the guide →

File format basics

Concepts worth knowing before choosing a file format.

Character encodingCharacter encoding maps text to bytes. If a CSV or TXT file opens with garbled characters, check the encoding expected by both the writer and reader, including UTF-8 and any byte-order mark.Container vs codecA container packages media streams, while a codec encodes audio or video inside it. MP4 or MKV alone does not tell you whether a device supports the internal codec.File compressionCompression reduces storage or transfer size. An archive such as ZIP can bundle files; a media codec may compress the content itself. Check compatibility and extraction needs.File extensionsAn extension such as .jpg or .pdf is a filename hint, not proof of the file's contents. Inspect the actual format before changing an extension or trusting a download.File formatsA file format defines how data is represented and interpreted. Choose one by the recipient's software, editing needs, fidelity and long-term access, not by extension alone.Lossless and lossy compressionLossless compression can restore the original data; lossy compression discards information to reduce size. Keep an appropriate source file when future editing matters.MIME typesA MIME type identifies the kind of content, often as type/subtype such as image/jpeg. It helps browsers and services handle files, but should be checked against the actual content.Raster vs vector imagesRaster images store pixels; vector images describe shapes. Photographs usually suit raster formats, while logos and diagrams often benefit from vectors that scale cleanly.Image transparencyTransparency lets the background show through parts of an image. Check whether the format and destination preserve an alpha channel; JPEG does not provide ordinary transparency.Numeric precision and conversionLarge integers and decimal fractions may change when a receiving program parses them into a limited-precision number type.Metadata, sidecars and external dependenciesMetadata describes content or settings. Distinguish a separate sidecar from external data needed to load a file, and check where each item is stored.What checksums can and cannot verifyA hash is calculated from file bytes. Compare with a trusted expected value using the same algorithm, separately from content inspection and sender verification.

Look beyond the format name

Narrow down by purposeCheck where each format works well and what to watch out for.

Compare similar optionsReview differences in size, compatibility, and editing.

Check the evidenceFollow the references and specifications on each page.