> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark-6/system-requirements-and-install.md).

# System Requirements & Installation

## System Requirements

Spikemark 6 is a lightweight application which runs on Microsoft Windows. As with almost every computer spec, the higher the better, but you don't *need* a full on gaming laptop or CAD station to run Spikemark successfully.

Below are suggested minimum computer specs:

* Windows 10 or 11
  * Older version of Windows likely work, though have not been fully tested
* Intel i7 or better with a minimum 16GB of RAM
* 256GB SSD (minimum)
* 4K Display (UHD 3840x2160)
  * A 2K (QHD 2560x1440) screen will work well too
  * 16:9 Aspect ratio is recommended
  * Rocking a laptop? make sure it supports a 2K or 4K external display
* Built in 10/100 Ethernet port
  * A USB to Ethernet adapter will do the trick

## Spikemark Installation

Installing Spikemark software is easy. [Download Spikemark](https://creativeconners.com/products/software/), then locate the downloaded installer `SpikemarkSetup_x_x_x.exe`. **Double-click** on the file and walk through the installer. For the recommended Standard Installation, follow the steps below.

#### Standard Installation

1. If you have a previous version installed, we highly recommend you uninstall first and then proceed.

![Uninstall Prompt in the installer](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-df5ad07d7af122c304fe0c73a4e943dc6a267c79%2FUninstallPrompt.png?alt=media)

2. Accept the License Agreement.

![License Agreement](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-61a7bd91d30d847c52f95744c175f30aab3833c5%2FLicense%20Agreement.png?alt=media)

3. Select the installation type. **Standard Installation is recommended for most users.** See [Advanced Installation](/docs/spikemark-6/system-requirements-and-install/advanced-installation.md) for advanced options.

![Installation Types](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-ba661dd448ead37e0748173fc586f17ba9b55632%2FInstallationTypes.png?alt=media)

4. Review the changelog for this version of Spikemark.

![Changelog](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-bc12a91aaf35a0de5138d686f199a0ae3c7e0bfa%2FChangelog.png?alt=media)

5. Select the 'Create a desktop shortcut' if desired.

![Desktop shortcut option](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-bd277a218c50114a5721507787c3ceb0eff2323e%2FDesktopShortcut.png?alt=media)

6. Confirm the installation.
7. Once the installation is completed, deselect Launch Spikemark and View Readme if you do not want to launch Spikemark immediately or read the release notes. Click 'Finish'.
   * *If you've selected an Advanced Installation option, you may be prompted to restart your computer instead.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.creativeconners.com/docs/spikemark-6/system-requirements-and-install.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.