MJPEG and JPEG cameras: stream or snapshot?

Identify which endpoint you have

Look for the manufacturer's description of the exact address you plan to use. A web page showing a camera image can contain controls and sign-in behavior that a viewer cannot use directly. Collect the documented stream or snapshot endpoint instead of copying the administration page address.

Axis documents /axis-cgi/jpg/image.cgi for JPEG snapshots and /axis-cgi/mjpg/video.cgi for MJPEG streams. These are Axis examples, not universal paths. Axis's video streaming documentation explains those requests and their supported arguments.

For an Axis camera, follow the Axis setup guide and check the device's own documentation. For any other brand, find its model-specific instructions before borrowing a path from another camera.

Keep a snapshot distinct from live viewing

A still picture tells you that an image request returned something. It does not show that the scene continues to update or that a viewer maintains a live connection. Record a snapshot result separately from a moving video result.

Ask what your task needs. A periodic visual check and watching a person move through a scene are different tasks. Do not rely on the appearance of one frame to decide which behavior your endpoint supplies.

For a test, arrange a visible change in front of the camera. Note whether the image changes without you requesting another snapshot. If you request another image manually, record that action too. Keep private scenes out of public issue reports; a written description of the result often suffices.

Collect address and account details

Write down the request scheme, camera address, service port, endpoint path and any documented parameters. Keep the account method beside those details. Ask whether the endpoint requires a viewing account, and use the manufacturer's documented procedure to create or select it.

Record the documented authentication method and picture settings for your camera. A viewer needs to handle the request and response the camera provides. Check the compatibility evidence before treating documented camera behavior as app support.

The app on this site is in development. MJPEG and JPEG are areas of protocol work, with validation still pending. The owner-supplied brief reports simulator captures of manual RTSP entry and H.264 fixture video. This website has not independently examined them; MJPEG streams and JPEG snapshots still need app tests.

Test one setting at a time

Begin with the manufacturer's simplest documented request on a reachable local network. Record the response or error, then compare any optional resolution or frame-rate settings as separate attempts. Avoid adding several query parameters at once when you are still investigating the endpoint.

If an image never appears, check the address, account and service before changing picture settings. If one image appears but the expected stream never updates, confirm the endpoint type and the viewer's documented behavior. Keep the two results separate in the troubleshooting checklist.

When the camera also offers RTSP, the RTSP viewing guide provides another set of details to investigate. A result on that protocol does not substitute for an MJPEG or JPEG test. If an iPad will show the image, use the iPad viewing checklist to record whether it updates at the screen size you need.