Anytype Docs
English
English
  • 👋Getting Started
    • Welcome
      • Mission
    • Install & Setup
      • Mobile
      • Vault
      • Key
      • Spaces
    • Objects
      • Blocks
      • Links
    • Types
      • Properties
      • Templates
    • Queries
      • Collections
    • Widgets
      • All Objects
    • Collaboration
  • Web Publishing
  • 📽️Use Cases
    • 🧠PARA Method
    • ✏️Daily Notes
    • 🍎Study Notes
    • 🎬Movie Database
    • ✈️Travel Wiki
    • 🗨️Language Flashcards
    • 🍛Recipe Book & Meal Planner
  • 🤖Advanced
    • Memberships
    • Features
      • Raycast Extension (macOS)
      • Custom CSS
      • Dates
      • Graph
      • Other Features
    • Data & Security
      • Import & Export
        • Migrate from Notion
        • Migrate from Evernote
      • Privacy & Encryption
      • Networks & Backup
        • Local-only
        • Self-hosted
      • Storage & Deletion
        • Bin
      • Data Erasure
      • Analytics & Tracking
    • Settings
      • Vault Settings
      • Space Settings
      • Keyboard Shortcuts
    • Community
      • Forum
      • Open Any Initiative
      • ANY Experience Gallery
      • Nightly Ops
      • Product Workflow
    • Help
      • FAQs
        • Any Timeline
      • Troubleshooting
        • AnySync Netcheck Tool
      • Beta Migration
    • Connect
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub

Web Publishing

PreviousCollaborationNextPARA Method

Last updated 2 months ago

Was this helpful?

You can now publish Objects as static web pages (HTTPS links) on your personal subdomain if you have *any name. These pages are uploaded to our servers as unencrypted HTML files.

This is an early version— linked Objects, and blocks like Queries and Collections aren’t supported yet. Multi-page publishing and other enhancements are on the way, and we’d love your feedback to guide these improvements.

Encryption

When users use web publishing, we upload objects unencrypted for a number of reasons:

  • Users explicitly choose an object to publish. So we limit the chance of accidental leakage.

  • If users want their website to be indexed by search engines, it should be plaintext.

  • The solution of decrypting in the browser and including the encryption key in the URL is a bit tricky in the case of multi-object exports.

  • We do rendering and caching server-side to limit resource consumption.

The object is decrypted locally on the device and then uploaded to the web publishing server in Anyblock format.

If you have files in your object, we include the encryption keys for those files. But because each file has a unique locally-generated encryption key, it doesn't compromise your account in any way.