Install & activate
Use an approved Release360 download, verify the package, install it, then sign in if your plan or workspace requires identity-bound entitlements.
DocuSphere360 PDF Studio — A KT Group Product
Explore verified downloads, Desktop and Cloud workflows, PDF editing, recovery, technical guidance, and the source-level API contract. Some advanced functions require certified releases and integrations, including Numerish eSign, AI assistance and cryptographically governed document revisions.
Start with basic document tasks, learn the three PDF Studio experiences, troubleshoot safely or inspect the developer contract. Each guide distinguishes generally available workflows from features pending release certification.
Desktop, Cloud, PDF editing, pages, OCR, forms, reusable signatures, version control and AutoSave360.
Read user manual → 02 · HELP & GUIDESStep-by-step recipes for editing, signing, redaction, crash recovery and support troubleshooting.
Open help & guides → 03 · DEVELOPERSSeven source-contract endpoints, permissions, draft and version conflicts, security and OpenAPI.
Read API reference → 04 · CONTINUITY & SAFETYLocal checkpoints, Cloud synchronization limits, missing keys, version reconciliation and customer consent.
View recovery guidance →PDF Studio is designed as a task-oriented workspace. You do not need to learn every module before starting. Open a document, choose the outcome you need, and follow the contextual workflow. Consequential actions such as redaction, signing, protection and governed publication include additional verification steps.
Use an approved Release360 download, verify the package, install it, then sign in if your plan or workspace requires identity-bound entitlements.
Understand File, Edit, View, Pages, Tools, Forms, eSign, AI, Governance and Help without working through every feature first.
Follow short guided recipes for editing, OCR, merge/split, redaction, PDF/A, comparison and signing.
Check release signatures, SHA-256 fingerprints, governed versions, evidence and security state before relying on a consequential document.
Prepare a signing package, add signers, route the request and retain signature evidence with the governed document record.
Use in-product Help or Numerish AI Support first. If unresolved, hand the conversation and diagnostics to Support360 as a governed support ticket.
The PDF Studio product page is the canonical public distribution entry point. Release360 exposes only Production-approved releases and retains version, platform and checksum history. If no release is listed for your platform, do not obtain an installer from another source.
Never install a “cracked”, offline-only, repacked or manually keyed copy. A genuine Pro or Sovereign entitlement is identity/workspace-bound and can be revoked when a lease, device or license becomes invalid.
| Platform | Approved distribution | Install flow | Verification |
|---|---|---|---|
| Windows | Numerish Release360 signed installer | Download → verify → run installer → launch | Publisher signature + SHA-256 |
| macOS | Numerish Release360 notarized package | Download → verify/notarization → install → launch | Apple notarization + SHA-256 |
| Linux | Numerish Release360 platform package | Choose certified package → verify → install | Release checksum/signing evidence |
| iOS / iPadOS | Apple App Store when published | Open store listing → install → launch | App Store distribution identity |
| Android | Google Play when published | Open Play listing → install → launch | Play signing/distribution identity |
Select your platform on the PDF Studio product page. Older Production releases remain visible in version history for controlled rollback support.
For direct desktop packages, compare the displayed SHA-256 with the downloaded file and verify the operating-system publisher signature where available.
Use the normal platform installer. Do not disable security controls, certificate checks or network protection as part of installation.
Free functionality can operate within its published entitlement. Pro/Sovereign users sign in with their Numerish identity so Account/Administration360 and License360 can resolve the purchased workspace entitlement.
PDF Studio validates plan, user, workspace, device and lease state. A mismatch does not become a valid license merely because a typed key looks syntactically correct.
License360 resolves entitlements from the purchasing account/workspace and binds allowed use to policy-controlled devices. This is deliberately stronger than “username + password + static key”. Offline use, where permitted, uses bounded signed leases rather than unlimited trust in a local key.
Core approved local PDF capabilities. No paid entitlement may be unlocked by entering an arbitrary key.
Purchased user/workspace entitlement, seat/device allowances and advanced PDF, OCR, AI/eSign allowances according to PricingHub/Subscription360.
Enterprise controls, governed revisions, evidence, deployment policy and higher-assurance licensing for regulated estates.
Desktop focuses on local PDF workflows; Cloud is designed for browser review and collaboration; the connected workspace binds permissions and revisions to the canonical DocuSphere360 document. The interfaces are related but not interchangeable release promises.
Open and manage device files with the editing, forms and page operations included in the verified installer. Native durable recovery is pending separately certified integration.
Scope authorized documents to a session, inspect previews and review context. Full editor and synchronized server recovery remain dependent on certified integration.
Honor tenant ACLs, version IDs, integrity hashes and maker/checker governance. The candidate bridge must be installed and certified before these endpoints can be used.
For the detailed tool comparison, see the platform and edition matrices.
Supported browser review drafts can be saved as encrypted local checkpoints and offered for restoration after a restart. This is separate from Cloud acknowledgment and from committing a new governed PDF version.
A supported draft reached encrypted browser storage in the original profile. It does not mean it has synced to the server.
After reopening, examine the document, draft timestamp and version. Restore only supported data, or explicitly discard it.
If the document changed, review the conflict. Never silently overwrite a newer PDF or alter a signature.
Browser review-draft recovery was tested in source-stage development; whole-PDF replay, Desktop native journals and Cloud draft synchronization require additional release certification. A local encrypted file alone cannot be decrypted by support without its appropriate key. Clearing browser data or losing keys may make recovery impossible.
Use the workspace by task. The availability of some commands depends on platform, document state, purchased plan, entitlement and organizational policy.
| Area | Use it for | Typical result |
|---|---|---|
| File | Open, save, Save As, recent files, export and print | Local or governed document output |
| Edit & Annotate | Text edits, highlights, comments, shapes and review markup | Revised working PDF |
| Pages | Insert, delete, rotate, reorder, extract, merge and split | Recomposed PDF |
| Forms | Fill, inspect and process PDF form fields | Completed form |
| OCR | Recognize image-based text and create searchable documents | Searchable PDF |
| Redaction | Mark and permanently apply removal of sensitive content | Redacted derivative/version |
| Protect | Apply permitted PDF security controls and protection policy | Protected PDF |
| Convert / PDF/A | Convert supported content and create archival-format output where certified | Converted or archival PDF |
| Compare | Inspect visual/semantic change between document versions | Difference review |
| Numerish eSign | Prepare recipients, fields, order, send and collect evidence | Signed package/evidence |
| AI | Summarize, extract, explain or assist with authorized PDF tasks | AI-assisted output subject to policy |
| Governance | Create a governed revision, hash, evidence and audit record | Verifiable document version |
| Help | User Manual, Help Guide, Tutorials, About, diagnostics and Support360 | Guidance or support ticket |
The in-app Guided Experience should surface the next best action for the current document. These recipes describe the expected workflow and the point at which an enterprise policy may require confirmation, permission or evidence.
PDF Studio integrates Numerish eSign as a governed workflow rather than treating a drawn signature image as proof. Identity, signer intent, routing, timestamps and resulting document evidence should remain associated with the signature package.
Open the final document, confirm the correct governed version and choose eSign.
Enter the intended signer identities, signing order and required signature/initial/date fields.
Check recipients, document version and permissions before sending the signature request.
Track status, receive the completed package and retain the eSign evidence with the document history.
AI functions are subject to plan allowance, organizational policy, privacy controls and provider availability. AI output should be reviewed by a responsible user before it becomes part of an authoritative document or decision.
Create an overview of selected pages or the current document, subject to permitted processing scope.
Identify structured information, explain selected content or assist with document understanding.
Entitlements, privacy policy, audit/evidence requirements and human review remain authoritative over AI convenience.
For governed workflows, PDF Studio does not silently replace the authoritative document. It can create a new version, compute integrity evidence and synchronize permitted history into the Numerish document/evidence services.
PDF Studio security is layered. Release360 controls what binaries are publicly offered; platform signing/notarization protects installer identity; License360 controls paid entitlement; document SHA-256 evidence protects exact document bytes; governed audit records preserve who did what and when.
Use only the official product page. Verify the SHA-256 shown by Release360 and the operating-system publisher signature or official store identity.
Paid functionality depends on signed entitlements and bounded leases. Revoked, mismatched or invalid licenses fail closed. Offline mode is not an unrestricted bypass.
Governed versions receive SHA-256 evidence so later verification can detect whether the exact document bytes have changed.
A visual black rectangle is not a redaction. Use the Redaction tool, apply the redaction, then verify the resulting document before distribution.
Local workflows minimize unnecessary transfer. Connected AI/eSign/governance features remain subject to authorized processing, policy and applicable privacy controls.
Operational errors may produce governed diagnostic events for authorized Observability360 and Numerish operational administration. Support exports should exclude document content unless deliberately authorized.
If an instruction tells you to disable networking, certificate verification, antivirus/endpoint protection or licensing services to make a key work, stop. That is not a valid Numerish activation procedure.
Confirm that you are signed into the purchasing Numerish identity/workspace, the subscription is active, the device is permitted and the system clock is correct. Reconnect so License360 can refresh the signed entitlement/lease. Do not replace it with a third-party key.
Permitted local capabilities may continue according to plan and a valid bounded offline lease. An expired or revoked paid entitlement does not become permanent simply because the device stays offline.
That means Release360 has no Production-approved public artifact for that platform/channel. Wait for an approved release; do not obtain an installer from an unofficial mirror.
Check source scan quality, language and page orientation. Always review recognized text before using OCR output as an authoritative record.
Reopen PDF Studio and use Help → Diagnostics/Support. Record the version, platform, workflow and time of failure. Where authorized, attach a diagnostic bundle to the Support360 ticket.
Compare the document SHA-256 against its governed evidence record and review version/audit history. A changed hash means the bytes are different, even when the page looks identical.
The PDF Studio bridge source describes seven operations for session, PDF preview, review comments, revision save and draft recovery. These are not yet registered as active production routes. Authentication, tenancy, key management and write gates must be independently certified.
Use PDF Studio Help → User Manual / Help Guide / Tutorial for contextual guidance. For unresolved problems, use Numerish AI Support and create a Support360 ticket. Include the application version, platform, workflow, timestamp, error reference and diagnostic bundle where policy permits.
Never send passwords, MFA codes, private signing keys, raw license secrets or unnecessary confidential document contents in a support ticket.
DocuSphere360 PDF Studio forms part of KT Group's portfolio of digital products and enterprise technology solutions.