What export formats and sharing options does MediaPeek provide?

Updated

MediaPeek lets you export inspected metadata as Object JSON, plain Text, HTML, or XML, and share results through an encrypted link. The export choice depends on whether a person or a tool will consume the output; the sharing option is for handing results to someone else without MediaPeek storing the content. Both features apply to metadata MediaPeek has already read from a URL, including files inside supported ZIP and TAR archives.

Export formats

MediaPeek describes four export formats, split between human-readable and machine-parseable output.

Format Best for What you get
Object JSON Scripts, pipelines, further processing Structured metadata as a JSON object
Text Quick reading, pasting into notes or chat Plain readable metadata
HTML Sharing a formatted view or embedding in a page Metadata marked up for browser display
XML Systems that expect XML input Metadata in XML structure

The site frames the choice as "the format that fits your workflow — whether you need something readable or machine-parseable." In practice:

  • Choose Object JSON when another program will parse the result, for example feeding track and codec fields into a catalog or a validation script.
  • Choose Text when you only need to read or forward the values, such as checking resolution and audio format before publishing a file.
  • Choose HTML when the result should render as a formatted page rather than raw text.
  • Choose XML when the receiving tool or template is built around XML.

The export covers the metadata MediaPeek has analyzed, not the media file itself. MediaPeek reads metadata using mediainfo.js (a WebAssembly port of the MediaInfo library, version 0.3.7, based on MediaInfoLib 25.10), so exported fields reflect what that engine reports.

Encrypted sharing

MediaPeek shares results through encrypted links. Per the site:

  • Sharing uses end-to-end encryption via PrivateBin.
  • MediaPeek does not store the content.
  • The key stays in the URL.

That last point matters operationally: anyone who has the full link can open the shared result, so treat the link itself as the secret. Send it through a channel you trust, and avoid posting it publicly if the metadata is sensitive. Because the key travels in the URL fragment rather than being held by the service, the sharing model depends on the recipient receiving the complete link.

How to use them

  1. Open the MediaPeek app and submit a URL — an HTTP/HTTPS URL or a public Google Drive file or folder. For archives, MediaPeek can look inside ZIP (Stored, DEFLATE) and TAR (standard and @LongLink) files without extracting the whole archive, keeping the archive name visible for context.
  2. Wait for the metadata analysis to complete. Fetching is partial: MediaPeek reads only the bytes it needs via byte-range HTTP requests, so large files don't require a full download.
  3. Pick an export format — Object JSON, Text, HTML, or XML — depending on whether a person or a tool will use the result.
  4. To hand the result to someone else, create an encrypted share link. Copy the entire URL, including the key portion, and send it to the recipient.

Common snags

  • Truncated share links fail. If a chat app or email client cuts off the URL, the key is lost and the result can't be decrypted. Verify the full link arrived intact.
  • Wrong format for the next step. Exporting Text when a downstream parser expects JSON (or vice versa) means re-running the inspection. Decide the consumer before exporting.
  • Assuming the link is private by default. The key is in the URL, so the link's confidentiality depends on where you send it.
  • Expecting the media file in the export. Exports contain metadata, not the underlying media; the partial-fetch design is about reading metadata efficiently, not retrieving full files.

MediaPeek is open source and maintained on GitHub, so the export and sharing behavior can be checked against the repository and its releases if you need to confirm details for a specific version.