Why are my VIGI FTP snapshots lower resolution than expected?

Often because the snapshot path is not using the stream or event behaviour the customer assumed. Stream settings, firmware and model behaviour all matter.

Should I check the sub stream too?

Yes. Comparing both streams is a sensible first step.

Will firmware matter?

It can, depending on the model and feature behaviour.

What if the customer needs better evidence images?

An NVR event clip or another capture workflow may be more suitable than relying only on FTP stills.

What should I record before changing any settings?

For TP-Link VIGI Camera FTP Snapshot Resolution Guide, record the exact model, firmware if known, current status, error wording, screenshots and the last known working condition. Change one item at a time so you can identify what actually helped.

Should I factory-reset the equipment while troubleshooting?

Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only when you have a configuration backup, known credentials and a model-specific recovery plan.

How do I confirm the problem is genuinely fixed?

Repeat the original test, then check the relevant local and remote paths separately. If the problem was intermittent, monitor through the conditions that previously caused it and record the successful result.

Support

TP-Link VIGI Camera FTP Snapshot Resolution Guide

When VIGI FTP snapshots look lower resolution than expected, the answer is usually in the stream path, snapshot behaviour or model limitations rather than in the phone app.

VIGI Advanced Setup

TP-Link VIGI NVR — On VIGI jobs, app and recorder support are usually tied together, especially after router changes or remote-viewing handover mistakes.

Summary

Use this guide when a VIGI camera is sending FTP snapshots, but the resulting images are smaller or less detailed than expected.

Applies to

TP-Link VIGI FTP snapshot use cases
Event snapshot workflows
VIGI cameras with cloud or local event delivery expectations

Difficulty and time

Difficulty: Moderate

Estimated time: 20 to 40 minutes

What you will need

Camera model details
Access to stream settings
Access to snapshot or event settings
FTP sample images for comparison

What this guide covers

Compare stream settings
Review snapshot options
Check model and firmware behaviour
Use a realistic workaround if needed

Customers often assume an FTP snapshot will always match the headline camera resolution. In practice, the snapshot behaviour may be tied to stream settings, event behaviour, firmware or how the system packages the image.

This guide explains the main checks and the practical workarounds without overpromising unsupported features.

Before you start

Check what the customer is actually receiving now before you change anything.

Compare the snapshot resolution against the main stream and sub stream.
Check firmware version if available.
Understand whether the snapshot is event-driven or scheduled.
Keep one sample file for reference before testing changes.

Important

Do not promise full-main-stream snapshots on every model or workflow

Snapshot behaviour varies. In some cases the system may not send exactly what the customer imagines from the headline resolution number.

If a workflow truly needs higher-quality evidence images, an alternative capture strategy may be more practical.

Step 1: Check the main stream and sub stream settings

Start by making sure the camera stream configuration matches the owner expectation. Some customers assume the FTP snapshot is always tied to the main stream when it may not be.

Record the main-stream resolution.
Record the sub-stream resolution.
Check whether the event path references one stream more than another.
Look for separate snapshot settings if available.

Step 2: Review snapshot and event settings

If the camera or NVR has separate event or snapshot settings, they may control what is actually sent to FTP.

Check any event snapshot options.
Check whether scheduled snapshots behave differently from event snapshots.
Confirm the event type that triggers the upload.
Retest after one controlled change at a time.

Step 3: Check firmware and model limitations

Some behaviour comes down to model capability or firmware stage, not a hidden menu item.

Check whether the firmware is current for the supported release path.
Review known feature notes for the model if available.
Do not assume every VIGI camera treats FTP the same way.
Document the current behaviour before escalating.

Step 4: Use practical workarounds if the workflow needs more detail

If the snapshot path cannot give the owner the result they want, another workflow may be better.

Consider full video export from the NVR where evidence detail matters more.
Consider whether an SD card or NVR event clip is the better record.
If appropriate, consider an external scheduled capture or NVR-based workflow rather than pure FTP stills.
Do not describe a workaround as a native feature if it is not one.

Common mistakes

Assuming FTP snapshots always equal the main-stream resolution.
Changing multiple settings at once.
Ignoring firmware version.
Selling an unsupported expectation to the customer.

Troubleshooting table

Symptom	What to check	What to do next
Snapshots are consistently small	Stream or snapshot path limitation	Compare main stream, sub stream and any snapshot settings first.
Quality changed after a configuration tweak	Different stream now referenced	Review recent changes and retest one variable at a time.
Customer needs higher-detail evidence	Workflow mismatch	Consider using event clips or another capture path rather than relying only on FTP stills.

When to contact support

Contact SecurityWholesalers support when you have the exact VIGI model, firmware version and current snapshot result, and you need help judging whether the behaviour is expected or not.

Related support guides

How to Add a TP-Link VIGI NVR to the VIGI App - Useful when remote access is part of the same job.
TP-Link VIGI 4G Camera Setup Checklist - Useful for remote sites using VIGI cameras in standalone deployments.

Related buying guides

TP-Link VIGI Buying Guide - Broader VIGI guide.

Relevant product categories

TP-Link VIGI Cameras - VIGI camera category.

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

Why are my VIGI FTP snapshots lower resolution than expected?
Often because the snapshot path is not using the stream or event behaviour the customer assumed. Stream settings, firmware and model behaviour all matter.
Is the FTP snapshot always the same as the main stream?
Not necessarily.
Should I check the sub stream too?
Yes. Comparing both streams is a sensible first step.
Will firmware matter?
It can, depending on the model and feature behaviour.
What if the customer needs better evidence images?
An NVR event clip or another capture workflow may be more suitable than relying only on FTP stills.
What should I record before changing any settings?
For TP-Link VIGI Camera FTP Snapshot Resolution Guide, record the exact model, firmware if known, current status, error wording, screenshots and the last known working condition. Change one item at a time so you can identify what actually helped.
Should I factory-reset the equipment while troubleshooting?
Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only when you have a configuration backup, known credentials and a model-specific recovery plan.
How do I confirm the problem is genuinely fixed?
Repeat the original test, then check the relevant local and remote paths separately. If the problem was intermittent, monitor through the conditions that previously caused it and record the successful result.