Verde Sync ROBLOX

Hello everyone! Today I want to introduce you to Verde Sync, a tool built specifically for Roblox developers, and completely free. With it you’ll get several features, from using it as bidirectional sync between your code editor and Roblox Studio, to using its Verde Cloud service to save your scripts as if they were a repository.

How it works:

  • Verde Sync uses a Roblox plugin and an extension that connect by creating a local server on your pc. Almost instantly, whatever you do in Studio is reflected in your code editor, and whatever you do in the editor is reflected in Studio. When you start it, the explorer is automatically created inside your editor, just like in Roblox Studio, and from there you’re ready to start working.
  • Verde Cloud is used only through npm, and with different commands (available in the documentation) you can upload your repositories, download them, create them, or delete them, whether public or private.

Features:

  • Verde Cloud: a “GitHub” like service for uploading the repositories of your Roblox Studio projects.
  • Auto-Folders: automatically creates your project’s folders so everything stays organized without you having to do it manually.
  • Native RemoteEvents creation: create them directly with no extra steps.
  • Security: a robust security system to keep your data and repositories as safe as possible.
  • Documentation: everything is fully detailed so you can use it without any hassle.
  • Easy to use: just download our plugin and, with npm or your code editor’s extension, you’re ready to connect.

Documentation: Verde — Sync Your Code Editor with Roblox Studio
Roblox Plugin: https://create.roblox.com/store/asset/92888643849408

If you have any suggestions or think something could be added, I’m open to hearing them.

What is Verde Cloud?

Verde Cloud allows you to package, backup, and share your code repositories directly from your terminal to our global infrastructure in milliseconds. Your projects will instantly appear on your Web Profile.


I do not see any terms of use, so that code being uploaded to another server effectively shares it so closed source projects could be viewed by you, and others on your service potentially.

I would recommend using git protocols, then the end user can completely control if their repo is private or public.

But uploading it to an unknown server would make this a big no from me. I do like the concept though.

Hi Acecool, thanks for the feedback—that’s a very valid point.

You’re right that right now there aren’t any published Terms of Use that clarify how uploaded code is handled, and that’s something that should have been there from the start. I’ll add it as soon as possible.

To clarify how it works: when you upload a repository with --private, only you (and the people you explicitly choose to share it with) can access it; it isn’t exposed or visible to other users of the service or to me. Repositories uploaded with --public do appear in the “Explore” tab for anyone to see, just as you’d expect.

I understand the concern about uploading code to an “unknown” server instead of using Git/GitHub directly, especially for closed-source projects. It’s a valid trust-based decision, which is why I want to be transparent about how everything is handled. I’ll work on documenting this better (Terms of Service, privacy policy, and how data is stored) so that anyone can make an informed decision.

Thanks again for pointing this out—feedback like this really helps improve the project.

1 Like