Skip to main content
Neural Defend

NeuroVerify Media Requirements

Image analysis supports JPEG, PNG, BMP, TIFF, WebP, and HEIC up to 10 MB, with at least 224 by 224 pixels and exactly one face. Video analysis supports MP4, AVI, MOV, MKV, WMV, FLV, WebM, OGG, and OGV up to 1.5 GB. Video sampling defaults to 12 frames, can be set from 1 to 100, and skips frames containing multiple faces. Validate locally where the official client supports it, but still handle server-side rejection.

Maintained byNeural Defend
Updated August 7, 2026
Siva Shankar, Co-founder and CTO of Neural Defend.
Siva ShankarCo-founder & CTO
An article-specific diagram for NeuroVerify Media Requirements organizes key sections including image inputs, video inputs, validation is a boundary, not a verdict.

Image inputs

The OpenAPI contract lists JPEG, PNG, BMP, TIFF, WebP, and HEIC for image analysis. The maximum is 10 MB and the minimum resolution is 224 by 224 pixels. Exactly one face is required, and EXIF rotation is corrected automatically.

The repository client documentation also recognizes HEIF in the documented image family. Because the OpenAPI format list and client guides can evolve independently, use the selected client release as the input contract for local validation and the API schema as the wire contract.

Video inputs

The video operation accepts MP4, AVI, MOV, MKV, WMV, FLV, WebM, OGG, and OGV up to 1.5 GB. It samples frames uniformly, using 12 by default unless max_frames or sample_rate changes the request.

Multi-face sampled frames are skipped. If no sampled frame with exactly one face remains, the API returns an unscored rejection. Audio is not independently returned for that rejected result.

An article-specific topic map for NeuroVerify Media Requirements organizes key sections including video inputs, validation is a boundary, not a verdict, image inputs.

Validation is a boundary, not a verdict

Local SDK checks can reject missing files, empty files, unsupported extensions, excessive size, invalid frame options, and unsafe path conditions before upload. Server-side validation can still reject quality, security, format, dimensions, or face-policy conditions.

Treat validation messages as recovery guidance. Ask for a corrected, authorized file when appropriate. Do not describe a rejected file as authentic or low risk because no score was produced.

Evidence boundary

Limitations

  • Media acceptance depends on the current client and server contracts; this page does not promise acceptance based only on extension, MIME metadata, or nominal dimensions.

Source record

Sources and references

  1. Neural DefendNeuroVerify media requirements in the OpenAPI contractVerified August 7, 2026.
  2. Neural DefendNeuralDefend Python SDK supported media and limitsVerified August 7, 2026.

Handle the response

Model every result state

Separate scored, rejected, error, and missing-modality outcomes before connecting analysis to a business decision.

Review API results