Point your agent at a file or a folder. Just Share shares it exactly as it is, and the recipient’s browser does the rest.
Prepare a folder
A folder works when it holds finished files a browser can open by themselves.
The recipient’s link opens one file, the entry file you choose. A photo set or
other multi-file folder needs a page that links to the files, such as an
index.html gallery. Ask your agent to prepare that page and choose it as the
entry. Just Share doesn’t build a gallery or listing for a folder. A site or
prototype needs a little more:
- For a site, share the build output. That is the folder your build tool
writes, often
dist,buildorout. A project root with source code is not a runnable preview, andnode_modules, build configuration and.envfiles or other secrets must not be selected. - For a site, include the page that opens first. Most sites use
index.html. Your agent tells Just Share which file that is, and it must be one of the files in the folder. Putassets/and any other files the page loads in the same folder. - Keep file paths simple. Each folder and file name can use letters, digits,
_,.and-, and must start with a letter, digit or_. A path can be up to 512 characters, and a share can hold up to 256 files. Spaces, accents and names that start with a dot, such as.envor.DS_Store, aren’t accepted.
If one file has a name that isn’t accepted, the whole share is refused and no
link is created. Rename the file and update whatever refers to it, or rebuild
the site with simpler names, then ask your agent to try again. For example,
rename Team Photo (1).png to team-photo-1.png. If the page doesn’t need
the file, ask your agent to leave it out instead.
If the page still looks broken, open the returned link and check that every file it needs was in the folder you shared.
How each kind opens
| You share | The recipient sees |
|---|---|
| A prototype or static site: HTML, CSS, JavaScript, fonts and images | The page, running in their browser. Links between its pages work. |
| Photos and images | A single picture at full size. For several, the gallery page you chose as the entry, linking to the pictures. |
| Video | A player in the browser, if their browser supports that video’s format. |
| A PDF | The PDF in the browser’s viewer, if their browser has one. |
| Any other file: a zip, a data export, a design file | The file, which downloads as you shared it. |
Browsers differ in which video, audio and PDF formats they open, and a supported file type can still fail if its codec isn’t supported. Test the link in the browser your recipients are likely to use. A single-page app works when everything it needs is in its own files.
Just Share sends your files unchanged. It doesn’t convert, compress or transcode anything.
What belongs on a host
Just Share is for passing work to people. It is not an app host, and none of your code runs on its servers.
- Servers and back-end code. Node, Python or anything else that has to run outside the browser.
- Databases and sign-ins you run. A shared page can’t keep accounts or saved data for the people who open it.
- Your product’s real website. Put your public site on a host built for it.
How shared pages are kept apart
A shared page is served from a different address than the account site where you sign in and pay. The recipient sees it in a sandboxed frame under the Just Share bar, and the sandbox keeps the page from reading your sign-in or reaching your account. That separation protects your account. It doesn’t make a link private: anyone who has the link can open it.
Limits
On Free, each file can be up to 50 MB, everything you share can take up to 500 MB, and a link lasts 7 days after its latest successful publish or update. On Paid, files can be up to 100 MB, your links can take up to 20 GB, and you choose how long each link lasts. MB and GB are decimal: 1 MB is 1,000,000 bytes.
Account has the full plan comparison. The technical limits apply on every plan, and Share, update and delete says what happens when a share goes over one.