diff --git a/README.md b/README.md
index ee29fca9929d76a0e8c913c84c6928b5d84ecbad..3d5fb0ac7a8ffa49db826dd23d98295e32558a8a 100644
--- a/README.md
+++ b/README.md
@@ -28,8 +28,7 @@ For a detailed explanation of how git works, and how it can be useful for other
 #### Git Workflow
 As you get used to working in git, it may be helpful to visualize what you are doing as a repeatable sequence of steps. In addition to the guides above, you may find the graphic below helpful for your reference:
 
-
-<img src="https://elevationusvistttest.s3.us-west-1.amazonaws.com/gitcheatsheet.png" alt="git workflow" width=50%/>
+<img src="./git/images/gitcheatsheet.png?raw=true" alt="git workflow" width=50%/>
 
 ## Learn These Python Packages
 
diff --git a/git/git-1_why_we_use_git_and_gitlab.rst b/git/git-1_why_we_use_git_and_gitlab.rst
index f90cf1cd7d915e20bda34cb25d2043b1c0e2d0da..8a73681ce3563f4b36df80ea49dda070c46bce94 100644
--- a/git/git-1_why_we_use_git_and_gitlab.rst
+++ b/git/git-1_why_we_use_git_and_gitlab.rst
@@ -38,7 +38,7 @@ Diffs
 Git also automatically produces an output called a diff that shows the line-by-line edits made in each commit. Diffs pinpoint the exact differences between file versions and provide a powerful way to understand version details and commit messages left by users. Below is an example of a diff showing changes someone made to a text file called index.md. This diff shows us the updating_the_geo_nodes.md line was deleted and the version_specific_updates.md line was added . Notice how
 this diff identifies only the exact part of the line that changed, as the “ing” stays the same between commits!
 
-.. figure:: https://elevationusvistttest.s3-us-west-1.amazonaws.com/git/text-commit-ss.png
+.. figure:: ./images/text-commit.png?raw=true
    :alt: GitLab diff :scale: 50 %
 
 Diffs are only visible with git for certain filetypes. Git was origially designed to deal with code for software development, so filetypes associated with most programming languages work great in git. For example, git will track commits and diffs for files like…
@@ -67,7 +67,7 @@ If we make a commit with these files, we won’t be able to see the diff! Below
 commit history. However, the diff cannot show what changed. The user is stuck with figuring out the differences between the original file and
 this new version. The only information provided is the commit message, “Added point and changed date”. For large files, this limited information may not be useful enough to track changes. It is often difficult to manage large, distributed projects without seeing the diffs.
 
-.. figure:: https://elevationusvistttest.s3-us-west-1.amazonaws.com/git/shp-commit-ss.png
+.. figure:: ./images/shp-commit.png?raw=true
    :alt: GitLab diff shp :scale: 50 %
 
 What text-based filetypes should we use?
diff --git a/git/git-2_clone.rst b/git/git-2_clone.rst
index 2139567c84f3e8ee71f801a1e9b8bddc52261d72..8b729d03eb9ca13c379d95f0028af9ad6e72d1bb 100644
--- a/git/git-2_clone.rst
+++ b/git/git-2_clone.rst
@@ -57,7 +57,7 @@ clone, and copying what shows up under "https". Once cloned, you will have
 the contents of that repository inside a new folder within your chosen
 file directory. Note: This new folder will be your git repository.
 
-.. figure:: https://docs.gitlab.com/ee/user/admin_area/settings/img/clone_panel_v12_4.png
+.. figure:: ./images/clone_panel.png?raw=true
    :alt: Clone Repo GitLab
 
 
diff --git a/git/git-3_branch-commit-push.rst b/git/git-3_branch-commit-push.rst
index 123e56fa3e2cad235cb0aa6e30dddf9b29368820..4689e305d64f9e10d89ff5d770ba518f1d7a26c4 100644
--- a/git/git-3_branch-commit-push.rst
+++ b/git/git-3_branch-commit-push.rst
@@ -21,7 +21,7 @@ Now, if you type ``git status`` you should see, once again, that you are “On b
 
 |image0|
 
-.. |image0| image:: https://git-scm.com/book/en/v2/images/head-to-testing.png
+.. |image0| image:: ./images/branches.png?raw=true
 
 Borrowing from git’s documentation, “A branch in Git is simply a lightweight movable pointer to one of these commits. The default branch name in Git is master. As you start making commits, you’re given a master branch that points to the last commit you made.” But you can create as many branches as you want. You can read more about branches `here <https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell>`__.
 
@@ -119,4 +119,4 @@ That’s it!
 
 You should now see the updated end_of_tutorial.txt file with your name on GitLab on the develop branch!
 
-The process we just followed is visualized in this `cheat sheet <https://elevationusvistttest.s3-us-west-1.amazonaws.com/gitcheatsheet.png>`__. You can follow this each time you work on a file.
\ No newline at end of file
+The process we just followed is visualized in this `cheat sheet <./images/gitcheatsheet.png?raw=true>`__. You can follow this each time you work on a file.
\ No newline at end of file
diff --git a/git/images/branches.png b/git/images/branches.png
new file mode 100644
index 0000000000000000000000000000000000000000..08352d608587b76dad10295129aaac477e252210
Binary files /dev/null and b/git/images/branches.png differ
diff --git a/git/images/clone_panel.png b/git/images/clone_panel.png
new file mode 100644
index 0000000000000000000000000000000000000000..427224f5b780e27802721c2621cdde09a33826d7
Binary files /dev/null and b/git/images/clone_panel.png differ
diff --git a/git/images/gitcheatsheet.png b/git/images/gitcheatsheet.png
new file mode 100644
index 0000000000000000000000000000000000000000..1955856021fe60d48f80f7a3a6ab78cad80fb12e
Binary files /dev/null and b/git/images/gitcheatsheet.png differ
diff --git a/git/images/shp-commit.png b/git/images/shp-commit.png
new file mode 100644
index 0000000000000000000000000000000000000000..0fea42677bfff93671c6ca234a878f5d874d7316
Binary files /dev/null and b/git/images/shp-commit.png differ
diff --git a/git/images/text-commit.png b/git/images/text-commit.png
new file mode 100644
index 0000000000000000000000000000000000000000..67bf974c623a676bd867771e8c943615f4135930
Binary files /dev/null and b/git/images/text-commit.png differ