On an LMS with no outbound access, a package that requests a single external address ends up as a blank frame or broken text. Packages built with Xakar are put together with that in mind.
Everything a video package needs in order to play sits inside the ZIP. It does not fetch web fonts either — text is drawn with the system fonts already installed on the learner's device. Playback works with no internet connection.
By default a PDF package loads the PDF.js viewer from a CDN. For a closed network, choose bundle mode when you build it: the viewer and its worker go inside the ZIP and the package grows by roughly 1.6 MB. One caveat worth knowing — PDFs whose fonts are not embedded may still request character-mapping files from outside, so test the actual file before you roll it out.
Stating it rather than leaving it out. The translation feature in PDF packages calls Google Translate and needs a connection; read-aloud works without one. Packages built to the xAPI specification send statements to an LRS, so the LRS has to be reachable — an LRS inside your own network works.
SCORM 2004 4th Edition and xAPI. There is also a Custom format where you supply the completion code yourself, which lets a package report into something other than an LMS.
A package is a single ZIP file. However it reaches your network, that ZIP is what you register with the LMS. Only building a package needs internet access; opening the finished package does not.
The video file goes into the ZIP as it is, so package size tracks the size of the source video. Upload limits differ by LMS, so it is worth checking yours before registering a large package.
Signing up comes with free credits. Download the package you build and try it on your internal LMS.
Get started free