One video region and one live webpage region rarely share a small Android panel: the board usually plays one video at a time, and the browser engine takes the memory the video needs. Run one video per panel and rebuild the slideshow as an image playlist, or give each job its own screen.
One video region plus one live webpage region is the layout small Android panels refuse. The board gives each playing video a share of its playback capacity. A small panel usually plays one video at a time, and the webpage region is a full browser engine that takes the memory the video needs. One region renders and the other goes dark. The limit sits in the device, as the player vendor's own support answer says. The layouts that work are one video per panel with images beside it, or one job per screen, and this page shows how to pick between them.
Why will a video region and a webpage region not show at the same time?
Both regions compete for one small budget. A panel player in this class gives you one video stream at a time, and a webpage region runs a full browser engine that takes the memory the video playback needs, so one of the two regions comes up empty.
Your layout asks one board for two heavy jobs at the same moment. The MP4 region needs video playback. The webpage region needs an embedded browser with its own memory, its own layout engine and its own image decode. A phone or a desktop has headroom for both. The Android boards behind panel signage have close to none, so one region loses. The tell is that each region works with the other removed. Ask the same panel for two MP4 regions and it shows one video and leaves the second region blank, the same limit seen from the other side; why an Android player cannot show multiple videos at once covers that case in full.
Is the limit in the player app or in the device?
The limit is in the device: the player vendor's own support answer to this layout was that the number of videos a screen plays at once depends on the hardware.
When this exact layout failed in the field, that vendor answer was to move to hardware that can do the job. Budget one video stream per playing video. Treat a second simultaneous stream as something you test for on the actual panel, and treat a panel that plays two at once as the exception in this class, not the rule.
Why does a webpage region eat so much memory?
Because a webpage region is a complete browser engine, with HTML parsing, JavaScript, a JavaScript heap, image decode and compositing, all sitting beside a video that wants the same memory. On a small panel the two together cost more than the board has.
Your slideshow page is light as pages go: a folder of images and a timer. The region still carries a whole browser stack, and it idles at a weight a signage board feels across the whole layout. Installers see the same ending every time: the slideshow page takes the resources and the video region never appears.
Measuring the cost from inside the page is its own trap. The in-page figure performance.memory is deprecated and unreliable, and its standard replacement has its own browser support limits. For a layout decision, the number that matters is the device's own memory reading with both regions live while the page cycles its slides.
Is my problem the stream count or the video file?
Test the regions one at a time. An MP4 that fails when it is the only thing playing is a codec problem that re-encoding to H.264 MP4 fixes in most cases, and a video that dies only beside the webpage is the resource collision.
Run the checks in order. Play the MP4 with the webpage region deleted; a failure there is a codec or container problem, and fixing a video that plays over USB but not in the player app walks that side end to end. Then play the webpage alone and let it cycle through every slide. When each region passes alone and the pair fails, the layout is the problem, and no re-encode will change that.
What should I put in the second region instead of a webpage?
An image playlist does the job: export the slideshow frames as JPG, PNG or WebP, load them from a microSD card or a USB stick, and let them crossfade slide to slide, which reads as motion and leaves the video free for the video region.
Export the frames at the region's exact pixel size so nothing is scaled. The free IMD Signage Player is built this way: it plays JPG, PNG and WebP images and MP4, M4V or WebM video from a microSD card or a USB stick, with H.264 MP4 the one we recommend, and it has no webpage region to collide with a video. Slides crossfade by default, and the fade setting runs up to 5 seconds. If the webpage earned its place because you edit slides in one spot, the optional HTTPS sync covers that: it pulls a playlist from your own web server on a timer, so you change the images on the server and the screen follows. For matching any player to a job, start from how to choose a digital signage player.
Can I pre-render the slideshow into a second video?
Usually it will not work, because a pre-rendered slideshow is still a second video stream. The panel that dropped your webpage-plus-video layout will drop this one too unless its hardware plays two streams at once.
Pre-rendering swaps a browser problem for a playback problem. The pair now needs two video streams at once, which is above what most panels in this class play. The count varies by chipset, so the only way to know is to play the finished pair on the actual panel with real files. While you test, encode the way video bitrate for a signage player, tested before you deploy describes, and feed both regions the content you will really run, not placeholders.
Would a second screen solve it cleanly?
Yes, cleanly: one panel plays the video loop, the second plays the slideshow, and each screen runs a single job, which is the alternative-hardware route the player vendor pointed to when the device could not do both.
This is the honest answer when the page must stay live. Panel one plays the video loop full screen, panel two plays the slideshow full screen, and each device sits inside its budget by construction. You pay for a second player, a second mount and a second power drop, and you keep the right to edit the slideshow on the website. If the wall already carries two panels, the change costs you nothing but a playlist.
| Layout | Video streams in use | Browser in the layout | Where you edit slides | On a one-stream panel |
|---|---|---|---|---|
| Video region plus image region | 1 | none | card swap or server sync | works |
| Video region plus webpage region | 1 | yes | your website | drops a region |
| Two video regions | 2 | none | re-render the file | only if the panel plays two |
| Two screens, one job each | 1 per screen | on one screen | your website | works |
Example: what fits on one 50-inch panel?
On a 1920 x 1080 panel, give the video 1280 x 720 on the left and the slideshow a 640 x 1080 strip on the right: 1280 + 640 = 1920, so the two regions fill the full width with one video stream and no browser engine.
Set the canvas at 1920 x 1080. The video region takes 1280 x 720 on the left, vertically centered: (1080 - 720) / 2 = 180 pixels of background above and below it.
The slideshow region takes the remaining 640 x 1080 strip on the right at full height, with slides exported as 640 x 1080 JPG files so nothing is scaled. The panel now runs one video stream and no browser.
If the slides must animate, the pre-rendered 640 x 1080 MP4 version turns the strip into a second stream, and this is the panel that already proved it shows one of two video regions, so the animated version moves to the second screen and plays full screen at 1920 x 1080.
If the animation was optional after all, that second screen can instead run an image playlist: slides exported at 1920 x 1080, a crossfade of up to 5 seconds, pulled from your own web server on the sync timer.
What should I check before the layout goes live?
Three checks before the wall: play the MP4 with the slideshow removed, play the slideshow with the video removed, then run the finished pair through one full 8-hour shift on the actual panel before anyone calls it deployed.
Confirm the MP4 loops on its own for at least one full pass. Run the slideshow alone through every slide. Then run the finished pair for the shift with the real files on the real panel, and watch the device's memory reading while the page cycles. A layout that survives the shift on the bench survives the wall.
Recommendation: Run one video region per panel and rebuild the webpage slideshow as an image playlist, updated by card swap or by HTTPS sync from your own web server. Give the live page its own panel when it must stay a page, and pre-render the slideshow to video only after the actual panel has played two MP4 regions side by side through a full shift.
Questions
Does adding memory let a panel show the video and the webpage together?
Seldom. The number of video streams a board plays at once is fixed by its video hardware, so extra RAM adds none. Extra memory can relieve the browser side of the layout, but a pair that needs two streams, or a stream plus a heavy page, still meets the same limit. Test the exact pair on the exact panel before buying anything.
Will a faster internet connection bring the webpage region back?
No. The page loads and the video plays; what fails is the device rendering both at once. Network speed changes nothing about the stream count or the memory the browser engine holds. Once the slideshow images are loaded they are small, and an offline image playlist takes the network out of the question completely.
What if the webpage is the main content and the video is secondary?
Give the page its own panel and move the video to the second screen, so each panel runs one job. With no second screen available, keep the webpage full screen and reduce the video to a still frame in a small region, because a static image needs no video playback.
Why did the same layout work on a desktop player?
A desktop-class player carries more memory and more playback capacity, so it can host a browser region beside a video where a small panel cannot. The layout lives or dies on the device. Test the finished layout on the panel you will actually hang.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.