> For the complete documentation index, see [llms.txt](https://cicd-docs.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cicd-docs.gitbook.io/docs/key-features/3-ways-to-upload.md).

# 3 ways to upload

Here's a quick summary on how we've made uploading a file into [CI/CD Docs](https://bit.ly/cicd-docs) a much pleasant experience.

## Uploading from a computer

You may have already download the build and release definition files to your computer - and that's great! All you would now have to do is just upload these files and see the magic happen. A detailed how-to guide is mentioned here:

{% content-ref url="/pages/-LMleBrxTNFJjmm2\_Blf" %}
[Uploading a file from a computer](/docs/how-to/uploading-a-file-from-a-computer.md)
{% endcontent-ref %}

## Uploading via a URL

If you're build and release definition files is available via a publicly accessible link, you can paste the URLs into this app and upload it straight away. 

Read more in this how-to guide:

{% content-ref url="/pages/-LMlgJdWuMbDJ5ygyvwz" %}
[Uploading a file via a URL](/docs/how-to/uploading-a-file-via-a-url.md)
{% endcontent-ref %}

## Uploading via a dynamic URL

Similar to uploading via URL mentioned above, you can also supply the URLs of the build and release definition files (that are publicly accessible, of course) as a URL of this app. This clicking on such dynamic URLs will take the user straight to the build and release view skipping the upload step completely. 

This is really helpful if you want to produce a shareable link that you could send to your colleague or friend and when they click this link, they'll be directed straight into visualizing the build and release view. 

More details here:

{% content-ref url="/pages/-LMlgOsD6TALnIzbzHWa" %}
[Uploading a file via dynamic URL](/docs/how-to/uploading-a-file-via-dynamic-url.md)
{% endcontent-ref %}