Data and File Integrity: JSON Schema, Image Resizing, and SHA-256

Sample JSON is the start of a data contract

An inferred schema describes only the supplied example. A present property initially becomes required, and a sample array containing strings does not prove production data will never contain null or numbers.

Treat output as a draft. Add formats, enums, length and numeric ranges, optional fields, and more examples. Validate both good and intentionally bad records in CI before calling the schema a contract.

• Collect several representative samples.
• Review required fields with a domain owner.
• Make an explicit additionalProperties decision.
• Document schema versioning and change policy.

Pixel memory is the real resizing constraint

Canvas decodes a file and draws pixels into a new surface. That enables on-device WebP or JPG quality control, but memory demand follows decoded pixel count more than compressed file size. Very large images can pressure a mobile tab.

Re-encoding may remove EXIF, ICC profiles, and other metadata. This can help web publishing but may not suit print, evidence, or archival use. Preserve the original and inspect transparency, sharpness, and color.

• Preserve aspect ratio by default.
• Avoid unnecessary upscaling.
• Compare file size and visible quality together.
• Never overwrite the original.

What SHA-256 proves

Identical bytes produce the same SHA-256 digest. A match makes byte-level equality overwhelmingly likely, but only when the expected hash came through a trusted separate channel.

An attacker can publish malware with its correct hash. Hashing is not antivirus, a digital signature, or identity verification. Provenance needs a trusted signature or independently authenticated channel.

• Obtain the expected hash independently.
• Verify the algorithm and format.
• Do not execute a mismatched file.
• Use signatures for source identity.

Separate controls in one workflow

Validate structure with representative examples and schemas, resize a copy and inspect it visually, then record SHA-256 for the final deliverable. Structure, presentation, and byte integrity remain separate auditable controls.

No single step describes the whole security state. Add authorization, current malware protection, backups, source review, and domain approval in proportion to risk.