Integrations & embeds
Add an Open in Anyfile button to your README, link to a public file preview, or embed a viewer in your website. Files are read directly in the browser.
Click “Open link” at the top of the workspace sidebar, enter a public file URL, then click “Open URL”. Copy the preview link, README Markdown or iframe HTML and paste it into your content.
Open the workspaceChoose a public file
Use a direct HTTPS URL on your own website, object storage, a public dataset, GitHub Raw or any other host. The file must be accessible without login, and the host must allow browser CORS requests. A GitHub blob page is a web page, not a file URL. Keep the filename extension in the URL so Anyfile can select a viewer.
For public files, your host can send Access-Control-Allow-Origin: *. If it restricts access to specific origins, allow the Anyfile origin used by your integration (normally https://www.anyfile.top). A file that downloads in the address bar can still fail to preview if CORS is missing. Anyfile does not proxy requests to bypass source restrictions.
Try a working example
This public Iris CSV from seaborn-data opens in the table viewer. Try the button or the embedded viewer below; no local file is uploaded.
Copy an integration
README platforms generally support Markdown image links rather than iframes. Use the iframe on a website or tutorial that permits embedded content; set width and height to fit your page and keep a descriptive title.
Preview link
https://www.anyfile.top/en/view#file=https%3A%2F%2Fraw.githubusercontent.com%2Fmwaskom%2Fseaborn-data%2Fmaster%2Firis.csvREADME Markdown button
[](https://www.anyfile.top/en/view#file=https%3A%2F%2Fraw.githubusercontent.com%2Fmwaskom%2Fseaborn-data%2Fmaster%2Firis.csv)Website iframe
<iframe src="https://www.anyfile.top/en/embed#file=https%3A%2F%2Fraw.githubusercontent.com%2Fmwaskom%2Fseaborn-data%2Fmaster%2Firis.csv" title="Anyfile file preview" width="100%" height="600" style="border:0" loading="lazy" allow="fullscreen; cross-origin-isolated" referrerpolicy="no-referrer"></iframe>URL and language
Use /en/view for English or /zh-CN/view for Simplified Chinese; replace view with embed for the compact iframe page. Put the complete file URL in the #file= fragment, encoded with URLSearchParams. The code generator handles this encoding. Keep the fragment rather than moving the file URL into the page query string.
For stable examples, use a versioned object URL or a GitHub commit URL. Links reference existing public files; selecting a local file does not create a shareable URL or upload it.
Limits and compatibility
Public downloads are limited to 128 MiB, including responses without an accurate Content-Length. Viewer-specific decoding and memory limits still apply. The current URL entry opens one file; it does not fetch related textures, fonts, paired camera files or other dependencies. Open a local folder or multiple local files when those are needed.
Requests omit cookies, authentication and referrers. URLs containing a username, password, query string or fragment, and URLs requiring redirects are currently unsupported. Use a direct anonymous file URL.
An ordinary website can embed viewers that work without cross-origin isolation. Formats requiring SharedArrayBuffer or threaded WASM need the parent page and all ancestors to satisfy cross-origin isolation, plus permission for the frame. Adding allow="cross-origin-isolated" alone is insufficient. Use the embedded viewer’s “Open in new window” link when necessary. Browser and format support still apply.
If a file does not open
Check that the URL returns the file itself, works without authentication, has no redirect and permits CORS. Confirm the download is under 128 MiB and the filename has the correct extension. A successful download does not guarantee the format or encoding is supported. For missing related files, open a local folder; for isolation requirements, open a separate window.
Privacy
Files are downloaded directly from the source into the visitor’s browser and parsed there. Anyfile does not upload, store or host those files. The source host receives the visitor’s download request. File URLs use a fragment that is not included in the Anyfile page request; analytics and performance events omit the complete file URL, filename and contents.