Asset Hosting Limitation Affects Multi‑File Project References

CodePen's Project feature enables a multi‑file file system for front‑end applications, but asset hosting is restricted to Pro accounts.

Free users must host images, fonts, or scripts on external services, which means local file references in a Project may fail when the assets are expected to be served from CodePen's own server.

This creates uncertainty about whether the Project environment can reliably resolve asset URLs without a paid hosting plan.

Does the Project's file referencing mechanism treat external URLs the same as internally hosted assets? Is there a version‑specific behavior that prevents local asset references in Projects despite external hosting?