This Interface works all IP Camera brands and models as well as any imaging devices and front-ends like iVMS, NVRs or DVRs, that can supply Snapshots via HTTP and/or HTTPS and is compatible with any and all Internet browser capable devices running on any Operating System and using any browser. From Computers to Tablets to Phones and TVs. Different brands and models of IP Cameras can also be displayed and controlled, at the same time.

Note: Images can be any size. Some smaller images are used for some demonstrations here.

Any IP Camera owner can easily get and use All My Foscam IP Camera Examples Bundled Together With One Hour Of One-On-One Support To Implement Them Click Here!

Free SecureImageDisplay Version 4.0 - (Display Only). Display with Camera Controls is included with bundle above

Image sizes for the examples shown here are small for demonstration purposes. You can use any sizes.

Works with ANY IP CameraAccessible From ANY Computer, Laptop, Tablet, Phone and TV

This Interface works with ALL Foscam IP Camera models and virtually all other IP Cameras as well as any imaging devices that can supply Snapshots via HTTP and/or HTTPS.

This Interface is compatible with any and all Internet browser capable devices running on any Operating System and using any browser. From Computers to Tablets to Phones and TVs. Without the need to download/install any additional software and works instantaneously when accessed from any Internet browser capable device.

This interface also will work with workplace, Wireless Hotspots and other Proxies, that normally block access to your IP Cameras.

Here are the current features and options this Interface supports:

Instantly Works With Any/All Internet Browser Capable DevicesInsert Custom Logon Into Camera ImagesInsert Custom Dynamic or Static Text Into Camera ImagesTotally Secure With or Without Controls and With or Without HTTPSAlways Totally Secure Using Any Internet ConnectionSecurely Post Real-Time Camera Images Anywhere Even EmailsSecurely Display As Many Cameras As Needed At Same TimeFor Emergency Use When Stuck Using Other DevicesWorks Behind Corporate And Other ProxiesRequire Unique User and Password to AccessAllows HTTPS Access Even For MJPEG Based IP CamerasSet Time Limit for ViewingUse Any Size Automatically Refreshed Images Clickable or NotUse Automatically Refreshed Thumbnails Clickable or NotUse Any Size Static But Real-Time Images Clickable or NotUse Real-Time Images in Social Media Websites, Forums and BlogsExtended Access Restrictions for ALL Foscam IP Camera ModelsSave Last Real-Time Image From Foscam IP Camera To DiskReal-Time Image Request Throttling Auto-Recovery Display Last Image Saved When Camera Is OfflineAutomatic Image Percentage ResizeAutomatic Image Fixed Size ResizeInsert Date Time and Custom Text Into ImagesTime Zone Offset When Web Server Is In Another Time ZoneControlled Privacy Display Last Image Saved During Private TimesAutomatic Image Refreshing Using HTML Front-End ("Example Included")

If you don't already have a website or a web server to host things like this or to store your IP Cameras Snapshot images and/or videos via FTP. All the examples here are hosted by DigitalOcean which I have found to have great prices and support. No domain name is required and you get your own unique IP Address and it's your Web Server, NOT shared!Click for more details

Accessing your IP Cameras over an unsecure Internet connection or displaying your IP Cameras in webpages on websites can be a very risky proposition. "What you can't see CAN hurt you". When you communicate remotely or someone else communicates remotely with your IP Camera.

In many cases when using HTTP as the access method to access your IP Cameras remotely. The IP Cameras DDNS, IP Address, Port, User Ids and Passwords are exposed in the clear. As you can see below which captured IP Camera communications using a free tool. That anyone can download:

MJPEG Based IP Camera

H.264 Based IP Camera

As you can see in the above images. This information was exposed during ("normal") HTTP IP Camera remote access. Even when using the standard IP Camera interface that comes with the IP Cameras using HTTP access. Even when using many if not most 3rd party applications for your IP Cameras when using HTTP access. The same exposure can take place when others are accessing your IP Cameras from a webpage located on a website which you allow.

This opens up the potential for others who gain access to this information, to abuse and exploit your IP Cameras by being able to view your IP Cameras Snapshots, video and listen to audio, from your IP Cameras 24/7/365 at anytime.

Do you the IP Camera owner really want anyone to be able to be able to view your IP cameras video and listen to your IP Cameras audio, whenever they wish?

Worse. If someone manages to captured your IP Cameras DDNS, IP Address, Port, User Id and Password and that IP Cameras User Id was at least an Operator Level User Id for your cameras. Anyone can be constantly changing the position of your IP Cameras. Again 24/7/365 if those IP cameras have PTZ ("Pan/Tilt/Zoom") controls while also being able to view and listen to your IP Cameras 24/7/365 as well. What if they pass that information on to others? How many different individuals could be doing any of these things, at anytime?

Note: If your IP cameras are moving they won't trigger any motion detection alarm. If someone points your IP Cameras at the ceiling, odds are good that your IP Cameras won't be capturing anyone destroying or taking your property as well. So maintaining the ambiguity of any and all information about your IP Cameras location and User credentials, should be a top priority.

The very worse case scenario would be if someone were to capture the DDNS and/or IP Address and Port for your IP Cameras and any Admin Level User Id and password accessing your IP Cameras. They then would be able to do all the above, plus also dump your IP Cameras configuration information gaining access to ANY Email and/or FTP User Ids and passwords for them. Stored in your IP Cameras configuration.

Potentially allowing them to take over your Email account and/or abusing your FTP credentials to destroy files and/or any webpages they maybe able to access using that FTP access.

This interface allows you to avoid this from ever taking place even when using HTTP access or HTTPS Access from any Internet browser capable device. The latest version of this Interface also allows you to not only display your IP cameras securely but to also control them securely as well. This allows you to remotely access or others you allow from web pages on websites to remotely access your IP Cameras with complete and total ambiguity of what if any DDNS, IP Address, Port, User Id, Password is being used to access your IP Cameras using this Interface.

If you want to get a very good idea of the data which is normally exposed when communicating with your IP camera using HTTP Access. I suggest you install this free tool which will show you how often this information is normally in the clear:

Most likely you will be shocked when you run it while accessing your IP Cameras using normal methods.

You then can use the same tool above. While using the Interface examples here as well. To see that this Interface is totally secure even with HTTP access and it can be used with HTTPS access even with MJPEG based IP Camera models. Which is NOT normally the case.

Note: Currently. The MJPEG based IP Cameras don't normally support HTTPS access methods. So HTTP access is your only choice. This Interface however, does support HTTPS access to MJPEG based IP Cameras.

The H.264 based IP Camera models don't natively support all browsers for all Internet browser capable devices. Which means that securely accessing the H.264 based cameras from any Internet browser capable device is normally not possible as well. When using all your possible devices as well as if you wish to allow others to access your IP Cameras from a webpage using any of their Internet browser capable devices. Without the potential need to download/install and/or purchase specific software on a device by device basis.

As stated. This Interface is compatible with any Internet browser capable devices. From Computers to Tablets and Phones to TVs. Without any need to download/install any additional software for any Internet browser capable devices to use and access the Interface instantaneously. Using HTTP or HTTPS access methods for any IP Camera.

Note: Some demo IP Cameras can be down at times. Which I have no control over. If you see nothing using a link for an example here. Please try another IP Camera example link here. There are many different demo IP Cameras and examples here.

Live Examples Demonstrating Total Secure Display and Control for your IP Cameras:

Note: Check the timestamp for each image below. If the Demo IP Camera is offline ("Last image displayed from disk") you will not be able to view the camera in real-time if you click on that IP Cameras image shown below.

Click on any of the Eleven Foscam U.S. IP Camera demo images below to view a specific IP Camera in Real-Time using unsecure methods to allow you to see if you choose what IP camera information is normally exposed using other methods and HTTP access to your IP Camera. If the IP Camera in question natively supports HTTPS then even the unsecure Interfaces can be changed to use HTTPS vs. HTTP and be used securely as well.

Last Real-Time Images Stored On Disk Displayed - CDT Time

Live Demonstrations Showing ALL Foscam U.S. Demo IP Cameras At The Same Time Using Totally Secure Methods Using Automatic Refreshed Images:

Note: If you used one of the other links here already. Your browser may have cached an initial image from them. Normally. That cached image, would not be present for people being denied access.

If someone were to try to access the Interface that was not allowed to do so and they tried to grab Snapshots or Refreshed Snapshots from your Foscam IP Camera(s). There are Extended Access Restrictions you can implement and use with the Interface. To deny anyone access to the Interface directly. Even if they know the file location of the Interface on the web server.

Note: Check the timestamp for each image below. If the Demo IP Camera is offline ("Last image displayed from disk") you will not be able to view the camera in real-time if you click on that IP Cameras image shown below.

Click on any of the Seven Foscam.com IP Camera Demo images below to view a specific IP Camera in Real-Time using unsecure methods. If the IP Camera in question natively supports HTTPS then even the unsecure Interfaces can be changed to use HTTPS vs. HTTP and be secure as well.

Last Real-Time Images Stored On Disk Displayed - China Time

Live Demonstrations Showing ALL Foscam.com Demo IP Cameras At The Same Time Using Totally Secure Methods Using Automatic Refreshed Images:

Note: If you used one of the other links here already. Your browser may have cached an initial image from them. Normally. That cached image, would not be present for people being denied access.

If someone were to try to access the Interface that was not allowed to do so and they tried to grab Snapshots or Refreshed Snapshots from your Foscam IP Camera(s). There are Extended Access Restrictions you can implement and use with the Interface. To deny anyone access to the Interface directly. Even if they know the file location of the Interface on the web server.

One of the downsides of accessing your IP Cameras over insecure Internet connections or displaying "Real-Time" image(s) of your Foscam IP Cameras in Social Media sites, Blogs, Forums, Web Pages, Instant Messengers or even in Emails as an image or as links. Is that by doing so, you expose and show your Foscam IP Cameras DDNS and Port or ISP IP Address and Port and User Id and Password credentials for your Foscam IP Camera.

This Interface provides methods that resolve the above issues with future versions and functionality to come. Even while using HTTP unsecure access methods to any of your Foscam IP Cameras.

Secure Private Use

These images and their very secure methods. Contain no reference to your Foscam IP Cameras Model information, DDNS, IP Address, Port or Cameras User credentials on where the Foscam IP Camera images originated from or how they were obtained.

In fact. These methods can be used to check on your Foscam IP Cameras when you are using any Internet browser capable device that is using public or semi-private Internet access. Such as public WiFi access or even your workplace and other semi-private internet connections for your Internet connection at that time.

Where you do not trust or wish to broadcast ANY information about your Foscam IP Cameras when accessing them on any risky or potentially unsecure Internet connection.

Where by doing so. Could and can expose you to Identity Theft or other IP Camera abuses. If others could use that exposed information. To abuse your IP Cameras by changing their position and/or viewing their video streams and/or listening to their audio, at anytime and/or gain access to your IP Cameras configurations. Thereby and possibly ("Depending on the User Id Level you used to access your IP Camera when using those unsecure Internet connections") others could also learn your Email and/or FTP User Ids and Passwords for them. Why take that RISK on a unsecure internet connection when there no longer is a need to do so?

Note: Once someone learns where your IP Camera is located ("DDNS and/or ISP IP Address and Port") over an unsecure Internet connection. While also having any valid IP Camera User Id and Password information that was exposed because of using that unsecure Internet connection. They can connect to your IP Camera and based on the IP Cameras User Id level and Password that they ("Sniffed") and captured over a unsecured Internet connection. They can also determine what type of IP Camera is being used during that ("Sniffing") process.

At the very minimum, they would have unfettered 24/7/365 access to your IP Cameras video and audio streams anytime your IP Camera was online and still using that same DDNS and Port or ISP IP Address and Port and User Id and Password for that IP Camera, that they ("Sniffed") on that unsecure Internet connection. That's a "Best Case" scenario and definitely not the worse case scenario and for sure, not worth the risk.

Some corporate, workplace, Hotspots and other Internet connections or their proxies. May block and not allow access to ports other than ports 80 and 443. This gets around those blocks as well. Allowing you to always have access to your Foscam IP Cameras. From anywhere using any Internet browser capable device.

Secure Public Use

Here are methods to securely display your Foscam IP Cameras "Real-Time" in Social Media sites, Emails, Forums, Blogs, Web Pages, Instant Messengers and anyplace where you can include images or links in your post. As well as your own web pages which can now include "Real-Time" Snapshot images of your Foscam IP Cameras and/or automatically refreshing Snapshot images from your Foscam IP Cameras, at the intervals, of your choice.

Without needing to include or expose any reference to your Foscam IP Cameras DDNS, IP Address, Port or Foscam IP Cameras User credentials. With or without your own custom text and/or date and timestamp embedded in the actual image(s) displayed.

This is an excellent method for example. To display a current single image or automatically refreshed images of any Foscam IP Camera. MJPEG or H.264 based, in Real-Time, on a web page at the time a visitor visits and views that webpage. Without giving up any information about your Foscam IP Camera location or user credentials. While and when doing so.

Download

Both these examples require having access to a Web Server with PHP.

In some cases. Web Hosting services do NOT allow access to non-standard outgoing ports. Meaning a port other then port 80. If your Web Hosting service will not open a non-standard port to your current Foscam IP Cameras port. You will be forced to use port 80 for your Foscam IP Camera, to get this to work. The php script automatically checks and reports if this is the case.

Here are the nine files required for this Interface. All in a .zip file:

These examples below are using a 160x120 and 320x180 resolutions for live demonstration purposes. But you can display any camera resolution for your Real-Time Snapshots or automatic refreshed Snapshots of your Foscam IP Camera on Social Media sites, Blogs, Forums or anywhere that allows you to add an images and/or links to your post. Including your Emails.

Examples

Both examples below are using the same Interface with different configuration options.

First Example - Simple Proxy

The first example. Simply pulls a current image from your Foscam IP Camera in "Real Time" and displays it on the web page that references it. Left is Foscam FI8918W. Right is Foscam FI9821W-V2:

The images you see above. Are Real-Time images that were just created when you loaded and viewed this Forum post web page. Not old images from the past, when this post was created and posted here in the forum.

You can do the same on any Forum, Blog, Social Media Site, Web Pages, Instant Messengers and in Emails that allows you to include images and/or links in your posts. Including your own Web Pages.

Even if the you are not allowed to include images in your posts. You can instead include a link that when clicked on can display a Real-Time image of your Foscam IP Camera. With or without custom text included in those images. Without exposing any information about your Foscam IP Cameras DDNS, ISP IP Address, Port, User Ids or Passwords to do so. Example:

You can also use these same secure methods that do not expose any information about your Foscam IP Camera. Such as your DDNS, ISP IP Address, Port, User Ids and Passwords. To display your Foscam IP Camera using automatic Real-Time images that refresh at the rate you desire by embedding the logic in a Web Page or including a link in Social Media sites, Blogs, Forums and Web Pages, Instant Messengers and your Emails. With or without custom text. Example:

Note: You can display as many Foscam IP Cameras, at the same time as you wish. Each configured differently or the same. Each with or without custom text and using any combination of Foscam IP Camera models with each being the same or different sizes. In any display configuration you wish. With ALL Foscam IP Cameras being displayed. Using these totally secure methods.

The Web Server is not storing any image file on disk, in the above example.

This means that if your camera was offline or not available. That no images would be shown.

This example is simply acting as a go-between for where the images will be posted and the Foscam IP Camera. So that the location and User credentials for the Foscam IP Camera remain private and hidden.

Second Example - Custom Text - Automatic Throttle & Fallback

This example actually does create a single jpg file for each Foscam IP Camera on the web server, which is reused as needed. This can also help you control web server resources when using methods like this unlike example #1, which will try and pull a image, each and every time from your Foscam IP Camera.

This second example, has many benefits over the first example, shown here.

1. It stores the last real-time image received from your Foscam IP camera on disk ("With any changes you configured") so that IF your Foscam IP Camera was offline or not available. The last image stored on disk will be used automatically for image fallback and displayed automatically. Not letting anyone know your Foscam IP Camera is offline or not available. Assuming that your image is not using a timestamp of course.

2. You can set the number of seconds since the last real-time image received from your Foscam IP camera was written to disk to get a fresh image directly from your Foscam IP Camera. So that you can better control resources when/if needed. Only getting a fresh image from your Foscam IP Camera when or if the image on disk is greater then x seconds old. Automatically throttling real-time requests to your Foscam IP Camera.

3. Allows you to insert your custom text and/or a date timestamp into the actual image and store it on disk. Technically it's also possible to add your own logo to your Foscam IP Cameras images displayed, with few changes to do so.

4. Privacy. Say you don't want real-time images of your Foscam IP Camera displaying all the time. You can simply temporarily change the Password for the User Id that the Interface is using. In the Foscam IP Cameras configuration.

This will cause the Interfaces real-time request to the Foscam IP Camera when trying to get a real-time image to fail. Because the Interface will now be using the wrong Password.

With the Disk logging configuration on in the Interface. Then the last real-time image from your Foscam IP Camera will be used as the image displayed.

You then can at anytime later. Change the Password back to what the Interface is using and real-time images from your Foscam IP Camera will then be getting real-time images from your Foscam camera. Instead of the last image on disk.

Giving you privacy when you need it. While not displaying empty images while doing so.

5. You can access the last image stored on disk from the IP Camera directly.

The images you see above are "Real-Time" images that were created when you loaded and viewed this web page not old images from the past, when this Forum post was created. They also create a single image file on the web server for each camera, that is reused and updated when this happens and that file can also be accessed directly as well. If any of the IP Cameras above were offline or not available, then the last image received from that IP Camera would be displayed above automatically.

Again, with no exposure of where the Foscam IP Cameras DDNS, or IP Address that created the image is located or any User Credentials for the Foscam IP Camera that produced the image above.

If any of the above Foscam IP Cameras were to go offline or become not available. Then the last real-time image received from the Foscam IP camera which was stored on disk. Would instead be used automatically and presented. Instead of a real-time image. This allows nobody to know that your Foscam IP Camera is offline or not available ("Assuming that you are not including date and time in your images").

Only the last real-time image received from your Foscam IP Camera is saved to disk, when using the disk option in the configuration for the Interface. So there is not any file clutter going on with multiple images from the same Foscam IP Camera being saved on disk.

Note: If you use the links above to get the files created by the images above, multiple times. Your browser may cache the files when using the link. Because the request to get the files, are not a unique request. However, the images shown above. Will be unique each and every time your refresh this Forum post web page, because it forces the images to be unique.

Both of these examples are TOTALLY secure methods. Simply using different configuration options available In the Interface. Allowing you to view your Foscam IP Cameras over unsecure Internet connections as well as share images of your Foscam IP Cameras. While providing total ambiguity about your Foscam IP Camera Model and maintaining the privacy of the DDNS, IP Address, Port and User Credentials of your Foscam IP Cameras.

You can create different copies of the Interface configured to be used for different purposes for the same Foscam IP Camera and you can use this Interface to display multiple Foscam IP Cameras at the same time. You can also reference and use any images created by the Interface that are stored on disk as the last image directly.

Secure Images and Refreshed Images Using HTTPS

Note: Even with the Foscam H.264 based IP Camera models that do support HTTPS. There is no requirement to port forward the HTTPS ports for those cameras to use these HTTPS methods with this Interface. Instead the Interface will use your SSL certificate on your Web Site avoiding any certificate warnings. If you have a valid and not self-signed SSL certificate for your Web Site.

The Interface also allows you to access any Foscam IP Camera model even MJPEG based camera models using HTTPS if desired. Accessing your Foscam MJPEG based IP Camera models, using HTTPS is normally not supported.

This can be very helpful if you wish to add your Foscam IP Camera in HTTPS based Web Pages.

Please note the Web Site being used for the examples is using a self-signed certificate which is why you will see a warning when using the example HTTPS links below:

In some cases, if your images are sized correctly. You can even use this Interface as your profile picture in Social Media sites, Blogs, Forums other Web Sites and even with some Instant Messengers. Allowing you to have Real-Time images of your Foscam IP Camera instead of any static images you currently maybe using there.

Unsecure Methods

The methods below do not require having access to a web server. The actual HTML code can instead be stored on any browser capable device or even stored as an Email attachment and accessed from any browser capable device as needed. But they are also unsecure and not secure methods as the above examples are.

Here are methods that will work with ANY IP Camera that will simply display refreshed images of your IP Cameras in a web page at your selected refresh rates and sizes. It only requires 1 line of HTML code per camera:

This Interface supports both accessing your IP Cameras totally securely for private personal use or for public Internet use by others.

Totally Secure. Any sizes, shapes, locations and clickable or not clickable. Embedded in your cameras images as they display. Use as a marketing tool or watermark for your cameras. Viewable by any Internet browser capable devices from Computers to Tablets to Phones and TVs.

This may seem trivial at first. But imagine being able to have your Logo or images ("Actually embedded in your cameras live images being displayed") and that when specific Logos/Images are clicked on. They take you to specific places based on what Logo/Image was clicked on. Social media sites, other web pages. Your choices are endless.

Here is a live camera example using multiple Logos/Images, Custom Text, Date/Time and Camera Controls. The "Request More Info" Logo/Image button accepts a click or a touch on that Logo/Image button alone and the other Logos/Images or camera viewing area is not clickable and Logos/Images stay where they are, when the camera viewing area is moved or zoomed:

You could even embed Preset image buttons in the cameras images, that when clicked on, move to cameras view to specific camera views.

Live camera examples, without camera controls and where when the "Request More Info" Logo/Image button" is clicked on, it takes you one place and any other areas of the live cameras views, when clicked on, take you to another place.

It's important to note that this interface is dual purpose. It can be used to securely access your IP Cameras for personal use as well as in webpages on websites for public access securely by others. Using HTTP or HTTPS access modes even for IP cameras that don't support HTTPS. Never exposing any information about your IP cameras DDNS, ISP IP Address, Port or User credentials.

Here is an example of adding an optional transparent .png image for a help button that can be merged with your IP Cameras images. Which you can also make clickable as your IP Cameras images are being displayed in real-time. Both for static and automatic refreshing real-time images from your IP Cameras:

Live example below of the IP Camera used above. Using automatic real-time refreshed images from the same IP Camera. Once you use the link below. When you click on the "Help" button area you are taken to the first post here. Any other area in the IP Cameras image is not clickable:

The IP Camera being used above is a Foscam FI8904W. Which is a MJPEG based IP Camera that does not natively support HTTPS access methods. This Interface allows both HTTP and HTTPS access methods to be used with any IP Camera.

The server providing the HTTPS example below using the same IP Camera as above. Is using a self-signed certificate for demonstration purposes. So you will see a warning message because of that, when using the link below:

If you view the HTML source code for the above examples. You will see that absolutely nothing is exposed about the IP Camera being used in the examples. No DDNS, no ISP IP Address, no Port or User credentials are exposed or made known. Making the use of this Interface for private and public use to access your IP Cameras. Totally secure.

The Interface itself is also protected from direct use as well. Example:

Restricting how and where the interface can be used from. The Interface also supports forcing the username and password of your choice in order to access the Interface as an option. With as many IP Cameras being displayed at the same time as you choose.

This specific image used in these examples shown here for the help button, is in the public domain and is free to use and can be found, edited, resized and/or downloaded there. All at the same website below:

Just wanted to give you some idea of how easy it is to find/locate images in the public domain that can be used to merge with your real-time IP Cameras images. Without any need or requirement to be a graphics artist. Which you can also make clickable, if you desire or to simply use as a watermark or logo.

Complete details about all the abilities of this totally secure Interface for your IP Cameras ("Which are many"), can be found here:

Live demonstrations of using Hikvision Network IP Cameras in web pages on websites with PTZ ("Pan/Tilt/Zoom") and Preset controls. Which are compatible with any Internet browser capable devices using any Operating System and browser. No browser plugins or media players are required to ever be downloaded and/or installed at anytime.

Nothing about the Network IP Cameras are exposed when using any of the examples below. No IP Address, No DDNS, No Port or User Credentials.

Time limits can also optionally be imposed to use a button to prompt to continue after a set period of viewing time of your Network IP Cameras has been reached and/or to jump to another web page on your website. To better help limit bandwidth usage and/or abuse.

Two Hikvision live examples with PTZ, Presets and Zoom lenses: IndoorOutdoor ("Using 4 and 3 second interval delays respectively")

You can also optionally require mandatory User credentials using the values of your choice to access the Network IP Cameras on your website by your website visitors. Same Network IP Cameras and delays as above, User: admin Password: adminIndoorOutdoor

HTTPS vs. HTTP can be used as well. Please note that the test server being used for these examples is using a self-signed certificate so you will see a warning when using these example HTTPS links. Same IP Cameras and delays as above:

The total number of lines of code is less than 200 lines for both the client ("Browser side") and web server side combined, to provide all the functionality you see shown here using these examples.

Of course the delays being used in the examples can be removed and the default Network IP Camera images can be larger than the examples used here. You can use the PTZ and Preset controls with live full-motion video or use automatic refreshed images as the examples are using here in your web pages on your websites.

Any Hikvision Network IP Camera that has a RS485 interface can also use add on horizontal pan brackets for Hikvision Network IP Cameras that don't/didn't support PTZ when you purchased it. Like these examples:

This Interface can be used with any IP Camera/NVR/DVR/VMS that supports pulling snapshots using HTTP and/or HTTPS and is accessible from any Internet browser capable devices. From Computers to Tablets and Phones to TV's. That are using any Operating System and Browsers. Without downloading/installing any Plug-Ins or Media Players and IP Camera image refresh bandwidth can be controlled as well. Which makes it great for web pages in websites as well as for personal use from any of your Internet browser capable devices.

Examples:

Added live Axis IP Camera demos. Here's one that even allows you to start a train with all IP Camera controls:

The Interface supports both HTTP and HTTPS and optionally prompting for access. Even if the IP Cameras does not support HTTPS. Unique User Id and Password that has nothing to do with the IP Cameras can also be used. The example below is using a self-signed certificate so you will see a warning. User: admin Password: admin

4. Images/Logos can now be embedded in the cameras image from a local file or from a website using HTTP and FTP.

5. When embedding images from weather sites. A delay can be used that stores the weather image in a local file and only gets a fresh copy when the weather website updates their image. Some weather websites update their weather images every 20 minutes. So this reduces logo/image processing and overhead. By storing the weather image locally and only making a remote request as needed.